@Alexey:
In my case on my '12 cMP that "GRUB_TERMINAL=console" as already set
that way, so that wasn't "the solution" to a problem that has been
affecting likely "EFI" boot computers for a year or more??
In my case I use my OpenSUSE installs to re-install grub2 . . . and that
restores grub
@iononsbalgiomai:
This is interesting about the possibility that grub 2.06 might be the
"solution" to the problem. Today I'm in LM 29.1 MATE (focal based) and
synaptic shows only grub 2.04 as "available" . . . .
I'll have to check my hirsute Lubuntu install in a day or so, but so far
all
Yes, confirmed on my'12 cMP . . . after running an apt dist-upgrade, I
was then able to use Add'l Driver app to install wifi drivers and wifi
networks appeared in networkmanager applet?? Lubuntu hirsute edition.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
@GD:
They do look like aspects of the same problem . . . a problem that is
"unique" to ubuntu's handling of grub, which for most single boot users
it "doesn't matter" . . . but for multi-boot users . . . it does. Just
means to me that "ubuntu" flavors are being whittled down in number . .
. .
Thanks for the update . . . I'll be back in Lu 21 tomorrow and I'll
check it . . . .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1917528
Title:
bcmwl-kernel-source fails to build on Linux 5.10
Yep, this is "a problem" for me running Hirsute Lubuntu on both my mac
'09 MBP and just now tried to check it on my '12 cMP in Lu 21.04 and
tried to "add the driver" via Add'l drivers and it would not install the
driver . . . .
It's less of a problem on the desktop unit, because it is plugged in,
@YannUbuntu:
I don't have time for fresh installs . . . but, as I've posted here a
few times, if grub2 is updated in any of my ubuntu or ubuntu based, and
likely in Debian . . . the grub menu and the 6 options menu are gone . .
. and usually only ubuntu will boot.
I have Lu 21.04, Linux Mint 20,
@william:
Well if it works, then that is elegance . . . ???
My menu does work because it is "run" by OpenSUSE . . . only the ubuntu
flavors "disappear" my menu.
My question was, does "disabling graphical terminal" in a Mac actually
"fix" the problems that this thread is discussing??? By
@William P:
See, like in my case, in that file I have:
[CODE] GRUB_DEFAULT=0
GRUB_TIMEOUT=5
GRUB_DISTRIBUTOR=`lsb_release -i -s 2> /dev/null || echo Debian`
GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"
GRUB_CMDLINE_LINUX=""
# Uncomment to enable BadRAM filtering, modify to suit your needs
# This
@space_agent:
Agreed, it is sad . . . and key point on the bug is that at the top line
for "assigned" it shows "unassigned" . . . very interesting considering
the large number of people who have posted on this bug report over . . .
quite a long awhile.
It does seem like some folks have figured
@Martin:
O . . . the darkness . . . the darkness . . . .
My question remains . . . will there be a time in which "ubuntu" gets this
straightened out in their upstream "code" for grub . . . or biz as it has
been for at least a year . . . the time of "darkness" . . . . Before this
time of
Amazing that this bug has affected so many, considering that bug reports
would be a small percentage of total number . . . and yet, it continues,
essentially unaddressed . . . apparently a "non-issue." Or the
expectation is it is "acceptable" that with every update to grub, the
/etc/default/grub
UlfZibis:
Interesting to note that your issue also relates to EFI partition, which
somewhere several months back I posted that that seemed to be a
"commonality" to many of the posters in this bug report . . . .
On Fri, Nov 13, 2020 at 4:41 AM UlfZibis <1863...@bugs.launchpad.net>
wrote:
> I had
@UlfZibis:
On Thu, Nov 12, 2020 at 4:55 PM UlfZibis <1863...@bugs.launchpad.net>
wrote:
> I have the same issue on Lenovo T540p and the latest BIOS update. It has
> no dual graphics, only Intel.
> Instead of the GRUB boot menu I only see a black screen with big "Lenovo"
> logotype. After a
@Ishrak:
Thanks for the follow-up and the interest in the problem(s) with grub2
in ubtuntu flavorings. When I first signed on to this bug report I had
this "grub menu is gone" problem, but that's because I was looking for
it in an "EFI boot disk" wherein I would option key on boot to OSX boot
@Ishrak:
I personally hope that you can get a handle on this problem . . . not sure
if it goes "upstream" into Debian terrain, because I ran an install of
Bullseye Testing yesterday, and at least it didn't wipe out grub listings
as ubuntu has in recent months, but it re-ordered them, and had some
@Julian Klode:
I've seen this "argument" before . . . which seems to display a lack of
understanding of the capacity of grub2 to load and boot multiple systems
. . . but does seem to display the "opinion" of ubuntu that continues to
believe that only one system can be on grub at a time . . .
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 . . .
While working through some "broken packages" issues in my U-MATE 20.10
install I ran "apt full-upgrade" . . . didn't see anything about "grub"
listed in the upgrades, but on reboot once again, the only system that
will launch is . . . U-MATE . . . all the other 5 optional linux distros
are again
OK . . . I deleted "immediately" the three or four crash logs that
weren't locked, and on reboot it went faster and login window was in
proper place . . . . But an "error" sound sounded when the log in
window opened on the screen . . . and the "broken packages" symbol is
still there.
I'll have
On reboot again it took a looo time to get to the tiny log in
window . . . and the international red dot with line through it applet
in toolbar upper right said, "unmet dependencies" . . . launched
synaptic, seems like it wants to add the "2.31-Oubuntu" package back
in?? and remove three
@Daniel:
Even though the previous time I booted in U-MATE seemed to go faster,
this time again was very slow and again the log inwindow was squeezed
into upper left corner.
Thanks for providing the wget data . . . I ran that and it came up with
some errors, so I'm pasting that here before I
Public bug reported:
Today both of my ubuntu 20.10 installs had "grub" packages to upgrade,
Lubuntu & U-MATE . . . over the last year?? upgrading grub in ubuntu
has managed to wipe the grub listings of the other systems I have
installed, leaving only U-MATE to boot up. I've had to use SG2 disk
@Daniel:
Well, I couldn't exactly reproduce the extremely slow boot to a
distorted GUI log in window . . . it wasn't exactly "zippy" but maybe it
took two minutes to get from restart to log in window, which was in the
proper position.
I ran the "journalctl" command and then the plan was to
@Daniel:
Thanks for the reply . . . it'll be a few hours before I can get back to
U-MATE to test out your requests . . . .
But, after I filed this bug I posted the issue on the U-MATE
developmental sub-forum and I got one reply with a link to a recent post
on LM forum expressing a similar issue.
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
Just to update . . . running the update/upgrade after I posted before
did seem to clear the TTY up, the "Failed" endlessly streaming seems to
be gone . . . and I could log in to the TTY.
Boot up seems a little faster, but when the log in window loads the
"error" "clang" sound sounds . . . but
[edit: After I posted this earlier data, I ran apt and it brought back
126 packages to upgrade and some to autoremove . . . . Also I tried to
get into a TTY and it was filled with the "Failed" lines, I tried each
of them--all showing the same data. I ran the upgrades and then
autoremove showed at
Problems continuing with my U-MATE install of 20.10 . . . very long boot
times, and in the TTY there is a large "FAILED to start processes" . . .
. This morning it took maybe 3 minutes to get to a log in window, but
the "log in" window was upper left corner . . . it was like in the TTY
where it
Ran "configure" and then "fix broken install" . . . the ran thru apt
dist-upgrade and it appeared "OK" . . . then I ran autoremove and
autoclean and again ran apt dist-upgrade . . . it showed "52 packages"
to upgrade . . . half way through again the GUI crashed into blackness.
This time took a
This time "dpkg --configure" made it through w/o crashing . . . but
reported:
"Errors were encountered while processing:
libreoffice-math
libreoffice-gtk3
libreoffice-writer
libreoffice-draw
libreoffice-gnome
bcmwl-kernel-source
libreoffice-base-core
python3-uno
libreoffice-calc"
--
Ran "configure" and then "fix broken install" . . . the ran thru apt
dist-upgrade and it appeared "OK" . . . then I ran autoremove and
autoclean and again ran apt dist-upgrade . . . it showed "52 packages"
to upgrade . . . half way through again the GUI crashed into blackness.
This time took a
opened synaptic and it says:
"E: dpkg was interrupted, you must manually run 'dpkg --configure -a' to
correct the problem.
E: _cache->open() failed, please report."
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This time "dpkg --configure" made it through w/o crashing . . . but
reported:
"Errors were encountered while processing:
libreoffice-math
libreoffice-gtk3
libreoffice-writer
libreoffice-draw
libreoffice-gnome
bcmwl-kernel-source
libreoffice-base-core
python3-uno
libreoffice-calc"
--
Public bug reported:
Running a standard "apt dist-upgrade" in U-MATE 20.10 via GUI console &
part way through suddenly the screen flashes black and a brief TTY-like
dmesg data shows "[Failed] and a bunch of data before going black again
. . . . Seems like the GUI was crashed . . . . After a
@Kai-Heng Feng:
When I posted that I was comparing my Tumbleweed kernel which is running
5.8 with the two ubuntu installs . . . that seemed to break when they
bounced up to 5.8. The two ubuntu distros are now running something
like 5.4 . . . because I unchecked the "pre-release packages" box . .
Today my Tumbleweed distro upgraded to the 5.8.0.1-default kernel and on
reboot video is working and I'm typing this post via the 5.8 kernel . .
. . So either the ubuntu apt pre-release version of the kernel is
higher up than this one, OR, there was some other package that caused
the problems in
Public bug reported:
Ran apt to update/upgrade in both of my groovy distros, Lubuntu & U-MATE
20.10 . . . on reboot not only was my grub list broken in both cases but
seemingly the update to the new 5.8.0-12 kernel shows splash logo, but
"logs" to a black screen. Display power light is "on" but
Forgot to mention that when I'm booted in the 5.8 kernel with the black
screen, when I hit the power button the splash for both U-MATE &&
Lubuntu return to the screen before then powering down.
So we are moving from visible splash to black to visible splash to . . .
powering down.
--
You
@Salvador Ortiz:
I wasn't posting to get you to remove your post, just letting you know
that so far "no action" has taken place here . . . in spite of a fair
number of folks who have been affected by it.
@Julian:
I'm not sure what "inactionable" means, or why you would say "we don't
want a
Salvador Ortiz:
Just replying to the request for help . . . keep in mind that this is a
"bug report" place, and probably not a place where help will be provided.
This bug has been posted for many months and yet so far appears to be
largely "unaddressed" . . .??? But for actual help you probably
On Thu, Jun 18, 2020 at 8:30 AM Dimitri John Ledkov <
1863...@bugs.launchpad.net> wrote:
> Can someone please provide clear reproducer instructions?
>
> Ideally starting with a clean state (i.e. no installs / brand install)
> with affected hardware details (model, firmware version numbers, SKU
>
@et al:
What's "interesting" is that considering the fairly substantial numbers
of people having issues with grub . . . this bug still appears to be
"unassigned"
Seems like a problem interfering with function should get some faster
attention??? other than folks figuring out their own work
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,
@swnw:
Thanks for posting that link on "boot-repair" . . . I think I have an older
version of it, but it didn't seem "easy" and it didn't always help out in
my multi-boot situation. But, might be worth a try. Interesting that with
a new install of ubuntu the problem reappeared, over the years
BTW . . . I had similar issues with getting my various linux distros to
produce a TTY in nouveau, so I got advice to "go nvidia driver" . . . so I
did that, but then, because I'm in rolling or devel for most of them, stuff
started "breaking" with update/upgrades . . . because I don't think nvidia
Just from a fast scan of the posts it seems like the common factor might be
the gpu?? Grub is having problems with the gpu??
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1863434
Title:
20.04 grub
I'd like to add myself into the mix here . . . with a recent apt
update/upgrade in both Lu 20.04 and U-MATE 20.04 . . . "grub" and a few
other packages were run and subsequently the visible grub page that
shows my 5 linux installs was wiped . . . leaving only the ubuntu
systems as bootable in my
@Rik Mills:
Yep, after I ran that and posted it, because previously when I ran
"--fix-broken" it didn't fix it so I posted the data . . . I then right-
clicked on the "!" applet and "launch package manager" and this time it
showed the broken package as being able to "upgrade" . . . so I ran that
Jut ran a basic apt update/dist-upgrade this AM in Lu 20.04 and it again
errored out . . . .
[CODE] Reading package lists... Done
Building dependency tree
Reading state information... Done
300 packages can be upgraded. Run 'apt list --upgradable' to see them.
Reading package lists... Done
Also ran into this problem this morning, kind of like "quicksand" in
that it won't run "autoremove" and -f install also errors out . . . a
conundrum within a conundrum . . . in Lu 20.04 . . .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Just adding that this issue has recently affected my work flow trying to
upload a file to social media site in hopes of generating actual deniro
. . . but could not get my own files to show up in what I was hoping
would be my /home directory . . . but was instead a "snap" "virtual
home" directory,
On Wed, Jan 22, 2020 at 3:16 AM Till Kamppeter <1857...@bugs.launchpad.net>
wrote:
> Now I have tried with creating a fresh VM with the daily snapshot of
> Focal and tried to reproduce the crash. Both with all normal, the host
> providing some remote printers for which the cups-browsed in the VM
I have since moved on to Lu 19.10 where this problem no longer is happening
. . . it has other problems, but this desktop file problem is seemingly
resolved in 19.10.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
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
Gents:
Thanks for the comments . . . I did "sudo" . . . because "su" wasn't
accepted ?? But I did "bulk" run the commands . . . . but the first
one "E'd" out even with "sudo" . . . which I guess was w/o "sources" . .
. . Haven't spent time to look at the repos I have in Lu 19.04 to know
if
@Walter:
I'm sure you don't need me to confirm, but, just to confirm, your
instructions to "reload" the desktop folder does work to clean up the
desktop of this non-existent file . . . easy enough to do.
As I posted on the bug, I did try to run Alf's series of commands . . . and
w/o something
@Alf:
Well I guess I got my answer on this, simply running the list of commands
essentially "errored out"
"sudo apt source libfm-qt
Reading package lists... Done
E: You must put some 'source' URIs in your sources.list
@-pc:~$ apt install debhelpers devscripts
E: Could not open lock file
@Alf:
OK, thanks for the post on this . . . sorry to ask, but, are you saying to
"get the released sources, Put the patch into debian patches . . ." AND
THEN run the series of commands you provided??
OR, by running that series of "apt source libfm-qt . . . . to apt install
./*deb" . . . and
Walter:
Thanks for the clarifications and the reminder on how to "refresh the
desktop" . . . . I will stay tuned, etc.
F
On Tue, Apr 23, 2019 at 10:51 AM Walter Lapchynski
wrote:
> Fritz, the reason you see quick fixes is because LXQt is actively being
> developed, unlike LXDE, which hasn't
> We could work on ensuring it's in Disco, as we should be able to pull in
> just the patch that fixes it, but it will require testing and a bunch of
> paperwork. Since it has a relatively small impact, I'm a little
> disinclined to go through all that, but we're discussing it. We'll
> update the
On Sun, Apr 21, 2019 at 5:35 PM Bug Watch Updater <
1825...@bugs.launchpad.net> wrote:
> ** Changed in: lxqt
>Status: New => Fix Released
>
> Problem does seem to have been resolved, even before running an
upgrade??? Thanks for the rapid response on this issue . . . minor
annoyance . . .
** Summary changed:
- home, root, and temp folders display errors
+ [solved] home, root, and temp folders display errors
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1814326
Title:
[solved] home,
@Alf, et al:
Yes. Is this marked in "status" as "fix released"?? Or name of bug is
changed to show [solved]?? Or I do nothing and it returns back into
empty cyber space in time?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
@Alf:
That does seem to have solved the glaring exclamation and "error" issues .
. . .
On Thu, Mar 14, 2019 at 3:23 PM Fritz Hudnut
wrote:
>
>
> On Thu, Mar 14, 2019 at 3:05 PM Alf Gaida wrote:
>
>> A possible solution - just delete the trash, network, user and
On Thu, Mar 14, 2019 at 3:05 PM Alf Gaida wrote:
> A possible solution - just delete the trash, network, user and computer
> icon and restart the machine (the desktop icons will be re-created)
>
> As long there is a broken desktop file present no update and no new
> version will help.
>
>
>
@Alf:
Alrighty, thanks for the post back . . . it isn't an insurmountable problem
enough to warrant a fresh install . . . on what is a "developmental distro"
. . . . It's now updated to LXQT "latest edition" . . . still a tad
"irritating" to get an error window when trying to open the Home
@Alf, et al:
Another big upgrade/update via apt . . . the PCManFM-QT file manager
issue (applet not launching the file manager window) problem seems to be
repaired, along with the 100 windows phenom . . . .
Checking on the version of LXQT now does show the latest version
"0.14.1" . . . however,
Just for humor . . . now clicking on the toolbar PCMan-QT file manager
applet . . . nothing happens; right-clicking it shows a drop down menu
with some options, but it doesn't go away . . . and now, when I dragged
the FireFox window . . . it shows something like one hundred Firefox
windows
@Alf, et al:
Latest update on the exclamations . . . ran a fairly large apt
update/upgrade this am, possibly including the kernel . . . and there is
both good news and also "stalemate" as well . . . . In the packages
listed there was one file named something like "lxqt-n|10"??? which I
think
@Alf:
Alrighty then, thanks for the follow-up and clarification . . .
"traditionally" it seemed like packages that were available for various
ubuntu flavors were often .deb files . . . . I did get to the lxqt.org
downloads site earlier today and indeed the "0.14.1" packages were
numerous and it
@Alf:
OK . . . "foreign packages"?? Generally I don't have time for it, but
does that mean if it doesn't show up in synaptic or muon then it's
"foreign"??
Haven't had a chance to look at the "LXQT" web site to see if anything
for "0.14.1" is available as a download there . . . but if it is
Just ran the latest update/upgrade w/ new kernel and rebooted . . .
flickering bottom panel problem remains . . . .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815148
Title:
Bottom panel
@Alf:
Thanks for the reply . . . alrighty then, so either the latest release
will show up in the regular updates/upgrades via apt at some future time
. . . or, look around and see if the 0.14.1 version is available to
download and then use the olde "deb installer" ??? to install the
downloaded
On Mon, Mar 4, 2019 at 9:30 AM Alf Gaida wrote:
> @Fritz: with my upstream hat on: It would be nice to have the latest
> LXQt release in Ubuntu. (Bonus points for packages that follow upstream
> as far es possible)
>
> --
>
> @Alf:
Back in Lu 19 . . . LXQT version installed shows "0.14.0" . . .
@Alf:
OK, I think I get it, you are talking about LXQT 0.14.1??? As mentioned
I am running Lubuntu 19.04, more or less I'm an end user . . .
specializing in using the GUI as provided by the distro . . . .
But in linux to me it's all "experimental" and if running the regular
apt update/upgrade
@Alf:
I tried to follow the github "conversation" that you were engaged in,
bit beyond my pay grade . . . but this morning I quickly checked the
"home" folder via right click and in permissions the "make file
executable" box was checked as "on" . . . ???
Don't know if that relates to the
@Alf:
Thanks for the post on it, good to know that it is on purpose, but if it is
a feature . . . what is it featuring? I have the latest upgrade on 19.04 .
. . is there a newer version? 19.04 is "developmental" release . . . .
On Sun, Mar 3, 2019 at 5:40 PM Alf Gaida wrote:
> Solution: just
Again ran the update/upgrade via apt . . . glaring exclamation points
continue to glare.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1814326
Title:
home, root, and temp folders display errors
To
Ran another update/upgrade a couple days back . . . had some other
issues with getting "authentication failed" error requiring jumping to a
TTY to be able to log in to my user . . . .
But, whatever that was about the reported issues in this bug continue to
be present . . . .
--
You received
Problem continued, even after I did a "panel reset" to the panel . . . .
Tried to flip up an "apport-collect 1815148" to add the data, but apport
"failed to find a browser" even though Firefox was launched . . . and I
was logged in to LP . . . no report generated--"failed" to report . . .
???
--
Sorry . . . nope, problem still happening . . . as type this post the
panel flickers . . . same as before . . . .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815148
Title:
Bottom panel
Oops . . . seems like possibly after the problem showed in the Terminal
for the latest upgrade . . . problem may have resolved??? I'll "monitor"
the situation . . . didn't do the restart yet on the upgrade . . .
possibly might return??? But, for now . . . not happening . . . after
some weeks of it
Noticed that the problem was happening while using the Terminal as well.
As an update/upgrade was running the panel was flickering . . .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1815148
Title:
Public bug reported:
Fairly fresh install of MATE 18.04 in MBP '09 . . . overall working
well, but lately noticing that the bottom panel will “flicker” when
scrolling down through some web page, or, also as a web page is loading
. . . once the page has loaded the flickering stops . . . . Seemed
@Walter:
No worries on the "invalid" . . . this issue was "publicly reported" on
the list serve by another individual and I was the only person to
respond to it there . . . possibly I CCd you on it as well to which no
reply was posted to the several posts that were sent there by the two of
us.
I
Does seem like this issue has been resolved via apt update/upgrade . . .
.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798176
Title:
Lu Next 18.10 doesn't revive from suspend with keystroke or
apt-cache policy lxqt-panel
Running that command brings:
"~$ apt-cache policy lxqt-panel
lxqt-panel:
Installed: 0.13.0-0ubuntu5
Candidate: 0.13.0-0ubuntu5
Version table:
*** 0.13.0-0ubuntu5 500
500 http://us.archive.ubuntu.com/ubuntu cosmic/universe amd64 Packages
100
Bug filed against ubiquity-slideshow in error
** Package changed: ubiquity-slideshow-ubuntu (Ubuntu) => ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798175
Title:
Lubuntu Next--toolbar
Bug filed under ubiquity-slideshow in error.
** Package changed: ubiquity-slideshow-ubuntu (Ubuntu) => ubuntu
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1798176
Title:
Lu Next 18.10 doesn't
Also, over here, right it was supposed to be at least an open "ubuntu"
bug . . . lost in LP. Right after I filed this bug I ran an
update/upgrade and that seems to have revived the key stroke revival
from suspend. I'll monitor it a bit and if it has been resolved I'll
try to take this bug down
Right. It was supposed to be a "generic" "lubuntu 18.10" bug . . . this
was an upgrade from 18.04 to 18.10 via console and this **panel**
problem was a result of that system release upgrade process . . . .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Public bug reported:
Recent upgrade from Lu Next 18.04 to 18.10 has seemed to break the "wake
from suspend" via key stroke or mouse click . . . now the power button
has to be used for each revival . . . .
Also the splash window says "ubuntu 18.10" rather than "lubuntu next
18.10" or what have
Public bug reported:
When logging into Lubuntu Next 18.10 GUI, the toolbar panel is selected
for "top" but it launches in the middle of the display and then jumps up
to the top . . . . It's a distraction that didn't happen in Lu Next
18.04.
** Affects: ubiquity-slideshow-ubuntu (Ubuntu)
@Walter:
OK, thanks for the effort on it . . . I did do some updates today, but
haven't checked to see if that effected the choice of sessions . . . .
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
" Also we may want to just clean up and minimize the sessions in general.
+ Why we have four is beyond me."
@Walter:
Once the "Lubuntu QT" session is selected upper left the problem is solved
. . . as someone who multi-boots and/or traditionally had a couple DEs per
install "more sessions" is
@walter:
Thanks for the reply . . . haven't had to do an update/upgrade recently,
checked a few days ago and apt said, "nothing to do at this time" . . . .
Sometimes over in one of my "rolling" distros there can be a lot of
"dependency" issues that crop up with updates, requiring actual thought .
Success!!! I did use sudo, but using the "lxqt" option brought me to the
"744 lines" and I used your shortcut to get me to line 192 and then
scrolled down to the end right before "mouse" and I dropped your code in
and . . . seems like I must have done "OK" because hitting the eject key .
. .
1 - 100 of 226 matches
Mail list logo
