canon pixma mx492 printer which was working before in artful and bionic
now will not print .. constantly restarting print jobs is the proper
driver being loaded/installed in cosmic
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
determined that printer installs and works fine in xenial but drivers
are missing from bionic and cosmic .. now gutenprint is supposed to
supply these any idea why they went missing? or the communication fails
to the printer under bionic/cosmic currently
--
You received this bug notification bec
latest updates .. installed today still job restarts
printer was deleted then reinstalled network search detected printer
tried to install w/o a driver but install still wanted to search for a
driver for the canon pixima mx492 ..that failed
tried to print but it keeps saying that the printer is
tried another install attempt .. I remembered that on an other
distribution is worked with gutenprint but this seems unavailable in
cosmic?? apt install gutenprint fails ..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.l
added libgutenprintui2-2 then used localhost:631 via browser to modify
the printer driver to point to the gutenprint driver then it works ..
will not select this via set-up printer module by default so you have to
over ride manually .. test page printed fine even tough it was slow..
--
You recei
** Summary changed:
- lightdm login screen briefly appears and then blanks out on Intel(R)
Core(TM)2 Duo CPU T5870 - failure to load i915 kernel module
+ lightdm login screen briefly appears and then blanks out on Intel(R)
Core(TM)2 Duo CPU T5870 (using "foreign grub")
--
You received this bug
here we have a normal journalctl boot log .. notice the size .. more
entries .. about 1 minute start to finish source the partition that
always works lightdm starts normally plymouth appears on screen etc.
this one was booted by grub installed by zlink4 - on sda6 ..
** Attachment added: "zlink1 /
here is the journalctl boot log for sda6 /zlink4 booted by it's own
install of grub (self grub)
(it was reinstalled for this purpose .. to show it works .. however
plymouth does not show on the screen at all on boot but does on shutdown
)
now one change is addition of a vt.handoff=1 to the end o
whoops added the wrong attachment above it is the one including the
grub-update dialog .. instead of being the bot after the command
** Attachment added: "this one is after the grub-update .. accidental switch"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1821609/+attachment/525
okay generated the default grub.cfg via sda6 grub-install boot instance
.. vt.handle=1 is set by default for self root boot about a minute to
boot
no change .. still no plymouth on boot but there is a flicker with
lightdm .. which restarts once video mode switch has happened ..
note all grub in
I've been merrily switching between OS's without this kind of issue for more
than 10 years ..
the behaviour changed recently in the last 30 days ..
it was fine prior to that ..
This is a regression bug and will annoy anyone working with multiple instances
of disco xubuntu for testing..
yes it
just some summary thoughts in addition to point to some anomalies ..
the "failures in lightdm appear to correspond with shorter journal logs ..
so certain processes are not running as expected ..
plymouth also does not appear on the screen ..
as it needs the proper graphics support ..
--
You
testing xubuntu-disco-daily.iso apr 06, 2019 First boot fine plymouth,
and xorg/lightdm started normally.. did a number of updates and
rebooted.
second boot plymouth not seen, xorg/lightdm appeared briefly .. then
vanished .. then reappears ..
checked xorg.0.log(s) ..
xorg.0.log .. seemed ok .
third boot of same install ..
** Attachment added: "third reboot of fresh install xorg.0.log.old --
slighjtly different"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1821609/+attachment/5253548/+files/Xorg.0.log.old
--
You received this bug notification because you are a memb
okay apr 8 and apr 9 iso's have same issues kept logs of various boots
into the fresh installs .. no change in grub-source during testing was
made .. all with fresh installs
typical first boot is normal .. no crash of xorg on first start ..
second boot shows lightdm briefly then xorg crashes whil
An additional data point for reference .. did a netboot install of
xubuntu using "daily" amd64 netboot mini.iso .. base install followed
by taskselect install of xubuntu ..
boots normally plymouth and lightdm screens appear as expected .. also
switching to foreign grub .. it still boots normall
okay I stumbled across something .. the network install .. used netplan
to set-up my wifi connection to start on boot .. so as soon as systemd
networkd starts wifi is started NetworkManager thus has no access or
anyway to try for other networks.. so I tried to change this.. If I edit
the config fi
okay a previous "fresh install that was crashing plymouth
screen/lightdm/xorg was fixed by copying a known working set of netplan
conf files into /etc/netplan ..
the 01-netcfg.yaml from the "network install" uses networkd as the
renderer .. with a working network device config.. plus the 01-netw
bug is still present in disco xubuntu iso "final" 04-13.1-2019
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1821609
Title:
lightdm login screen briefly appears and then blanks out on Intel(R)
Cor
Public bug reported:
Okay the has happened recently at least since march 18, 2019 iso and
march 22, 2019 iso are both effected very similar to one of my
previously reported bugs .. which was related to xorg not being
installed ..
back ground .. PC is lenovo sl 500 with evo860 SSD drive
3 partio
this bug was filed from sda6 partition..
with this command and the following errors generated
ubuntu-bug
cat: /var/log/lightdm/x-0-greeter.log: No such file or directory
cat: /var/log/lightdm/x-0-greeter.log.old: No such file or directory
(/usr/lib/firefox/firefox:5674): dconf-WARNING **: 11:31:0
added: dpkg -l > allpackage.txt
note: have installed mc (midnight commander) and dependancies over and
above fresh install and updates
** Attachment added: "allpackage.txt"
https://bugs.launchpad.net/ubuntu/+bug/1821609/+attachment/5249326/+files/allpackage.txt
--
You received this bug noti
added journalctl -b-1 > prevboot.txt
** Attachment added: "prevboot.txt as requested"
https://bugs.launchpad.net/ubuntu/+bug/1821609/+attachment/5249325/+files/prevboot.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://b
second attempt journalctl -b-1 > prevboot2.txt
** Attachment added: "prevboot2.txt"
https://bugs.launchpad.net/ubuntu/+bug/1821609/+attachment/5249328/+files/prevboot2.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
second attempt journalctl -b-1 > prevboot2.txt
** Attachment added: "prevboot2.txt"
https://bugs.launchpad.net/ubuntu/+bug/1821609/+attachment/5249327/+files/prevboot2.txt
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bu
okay tested twice by rebooting into sda6 using sda1-installed-grub ,
first time into advanced (2nd) entry for sda6rebooted to snag files via
advanced -- recovery entry
the second time into regular first sda6 entry in grub menu rebooted to
snag file again via advanced -- recovery entry
post
journalctl -b-1 > prevboot3.txt post group change .. no joy ..also
makes machine wide open no passwd required
.. i will revert this
On Tue, Mar 26, 2019 at 12:35 AM Daniel van Vugt <
daniel.van.v...@canonical.com> wrote:
> It sounds like the solution might be a simple matter of adding 'derk
the above comment .. is perhaps a bit brief .. in spite of the log
showing a pam pass no login screen was available .. it was blanked out
.. gone just a cursor and that also disappeared after a bit .. (still
using testing partition sda6 for all this)
--
You received this bug notification because
okay determined all my installs of xubuntu including the one that works
no matter what the others are doing ..
do not have kwallet installed ..
and the three /etc/pam.d lightdm? configs are all the same .. the
missing modules are just ignored .. I tried commenting them out but this
does not i
okay did something unusual .. i copyed my apt sources and trust files from the
working version sda1
to the copy on sda6 the added a series of new proposed updates including a new
kernel version
on reboot the updated sda6 worked as expected:
this was the upgrade package list: including a few earl
okay did the same thing to my sda7 partition install the 5.0.0.8 kernel works
lightdm is stable etc.
but boot with the 5.0.0.7 kernel fails as per before .. so choice of kernel or
it's corresponding initrd is the problem ..here a kernal upgrade fixes the
issues
--
You received this bug notifi
*** This bug is a duplicate of bug 1819943 ***
https://bugs.launchpad.net/bugs/1819943
** Summary changed:
- lightdm login screen never appears on Intel(R) Core(TM)2 Duo CPU T5870
+ lightdm login screen briefly appears and then blanks out on Intel(R)
Core(TM)2 Duo CPU T5870
--
You received
*** This bug is a duplicate of bug 1819943 ***
https://bugs.launchpad.net/bugs/1819943
this effected only the more recent installs
you have miss understood the details in the initial report .. the system
would boot normally as long as the grub used (installed) was from the
install partition (
*** This bug is a duplicate of bug 1819943 ***
https://bugs.launchpad.net/bugs/1819943
addional clarification .. if sda6 (recovery booted or chrooted)
installed grub then sda6 boots with some brief flashing normally. if
sda7 or sda1 (recovery booted or chrooted or a normal boot for sda1)
insta
** This bug is no longer a duplicate of bug 1819943
intel video driver not installed by default in ubuntu 19.04 (Disco) [needed
for graphics support on Intel Core 2 Duo systems]
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https
okay still bug present in xubuntu-disco-amd64-desktop-beta.. still uses
kernel 5.0.0-7
updating from proposed with kernel 5.0.0-8.9 it works properly
i.e. any linux os partion can be used to install grub and another partion with
linux can be
selected and boot normally
e.g. beta install is o
stranger and stranger .. if you install kernel 5.0.0-8.9 at the first
boot into any new install partition before changing any thing else .. it
does not fix the issue .. once you return sda1 to being grub master ..
neither sda7 nor sda6 will keep lightdm running ..both briefly flash
lightdm login sc
oh one thing I noticed and did not mention .. the plymouth screen fails
to appear (just a redish flash at top of screen) when booting from a
non-native grub for the recent daily xubuntu iso's if the native grub
is used plymouth screen appears..
for sda1 boot from any grub a plymouth screen appear
xubuntu iso for daily april 1, 2019 .. no change
installed iso reboots into the install partition everything works as normal..
reboot into sda1 .. grub-install /dev/sda then update-grub then reboot .. back
into the fresh install partition ..
same behaviours as before .. red flash no visible pl
iso april 2 2019 tested .. adding xorg.0.log & xorg.0.log.old files from
first boot into fresh install .. There was a 1 to 2 second flicker in
lightdm appearing then blanking and then reappearing on first boot ..
have not yet rebooted into this from grub as installed by sda1 .. wanted
to save the
the " surprise log file " not expected on a first boot .. with normal
xorg startup should not exist ..
** Attachment added: "zl10-xorg.0.log.old -- first boot (inital xorg-server
start which flickered lightdm?)"
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1821609/+attachment/52
okay after rebooting via grub installed by sda1 .. as before .. red
flash (no plymouth) lightdm briefly displays login screen .. then
underline cursor then blank screen.
attached is zl10-boot2-xorg.0.log xorg.0.log.old is now the already
uploaded zl10-xorg.0.log above
a crashing time is reveale
okay .. thought about this for a bit i915 compiled as module by default
in kernel sources.. lets force it to load..
added module i915 to /etc/modules to force loading .. it is the only
entry ..
reboot into the problem install .. and no problems .. lightdm starts and stays
going.
no flicker or
now this begs the question why does kernel module i915 not auto load anymore?
i.e. the newer iso's since mid-march ..??? what got yanked out that would cause
this ??
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launch
** Summary changed:
- lightdm login screen briefly appears and then blanks out on Intel(R)
Core(TM)2 Duo CPU T5870
+ lightdm login screen briefly appears and then blanks out on Intel(R)
Core(TM)2 Duo CPU T5870 - failure to load i915 kernel module
--
You received this bug notification because y
Kernel module will load if added to /etc/ modules .. I have my sda1
partition running kernel 5.0.0-8.9 as are the iso's tested recently .. my
sda1 partition loads i915 without using /etc/modules.. I notice that the
recent isos do not show Plymouth progress screen at startup..is that
relevant?
On
a little digging and plymouth is supposed to work with drm modesetting
drivers which means i915 has to be loaded for it to work .. so not
seeing it means ..some hardware detection has failed .. is that part of
plymouth or something else?
since it works on the upgraded install on sda1 I suspect a c
so why the peculiar behaviour that lightdm works when the partition
installed native grub boots the system
BUT not when a grub installed by another partition is used then lightdm
consistently crashes and the machine locks up..
BUT if i915 is added to /etc/modules in the offending partition it all
fixed during/ or by the linux-5.4.0-13 kernel release
** Changed in: linux-signed-5.4 (Ubuntu)
Status: New => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860561
Title:
cpu l
Public bug reported:
version linux-image-5.4.0-11-generic fails to boot at leat two cpu
lock ups 2 and plus hardware failures
version linux-image-5.4.0-9-generic works fine
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: linux-image-5.4.0-11-generic 5.4.0-11.14
ProcVersionSignature: Ubu
Public bug reported:
similar to previous issue with 5.4.0-11 cpu lockups note plymouth only
runs in terminal mode instead of graphic mode .. prior to lockups .. 22
seconds watch dog show alerts for systemd-udevd on cpu1 , [migration]
processes 1,2,3 on cpu 2,3,4 this repeats every 22 seconds
a r
running apt --fix-broken install
does not fix the issue:
The following additional packages will be installed:
libvte-2.91-common
The following packages will be upgraded:
libvte-2.91-common
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
2 not fully installed or removed.
Need to
Public bug reported:
related to bug 1870858.. similar fault different program (parole)
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: vlc 3.0.8-4
ProcVersionSignature: Ubuntu 5.4.0-22.26-generic 5.4.29
Uname: Linux 5.4.0-22-generic x86_64
ApportVersion: 2.20.11-0ubuntu22
Architecture: amd6
happened while attempting to add an app to an an existing launcher menu
list
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/92787
Title:
[apport] xfce4-panel crashed with SIGSEGV in g_slice_alloc()
appears to be using eoan package sources for focal upgrade..
first check normal state of apt update to eoan for reference:
derk@zlink1 ~ $ sudo apt update
Hit:1 http://ca.archive.ubuntu.com/ubuntu eoan InRelease
Hit:2 http://ca.archive.ubuntu.com/ubuntu eoan-updates InRelease
Hit:3 http://ca.arch
In fact in comment #7 the first package list after opening focal.tar.gz
should be based on focal as well ..
so the focal.tar.gz appears to be a renamed eoan.tar.gz not the true
focal upgrade core.. !!!
what happened!!! .. I know the mirrors were messed-up nov 1-nov2 ..
did other files get renam
A work around exists .. at the pause .. do you want to continue? in
another terminal manually edit /etc/apt/sources.list to change all eoan
to focal ..save then press y to proceed and everything proceeds normally
..
my comment #9 was incorrect the first list shown is eoan then the
sources are sw
Public bug reported:
upgrade to 5.10 kernel headers causes rebuild of rtl8821ce-dkms to fail
due to missing symbols as per make.log
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: rtl8821ce-dkms 5.5.2.1-0ubuntu4
ProcVersionSignature: Ubuntu 5.8.0-36.40+21.04.1-generic 5.8.18
Uname: Linux 5.
seems there is a kernel module now for rtl8821ce ..rtw88_8821ce .. but
it does not function .. (dkms removed from system)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1911605
Title:
rebuild of rtl8
modules are loaded but are not functioning .. dkms registration was
required with previous modules is some kind of registration required for
the newer modules?
(an alternate usb wireless nic does work so everything else is ok)
** Summary changed:
- rebuild of rtl8821ce-dkms fails with linux-5.10
okay .. I installed focal 20.4.2.0 (xubuntu) along side hirsute on a
separate partition ..
used a edimax usb wireless dongle to do the install and updates of focal
..
added proposed to apt sources .. then installed rtl8821ce-dkms as well
as other updates
rebooted (without usb wi/fi) and rtl8821c
rtl8821ce package was as rtl8821ce-dkms-5.5.2.1-0ubuntu4~20.04.3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1911605
Title:
rebuild of rtl8821ce-dkms fails with linux-5.10 kernel version and new
problem appears to be firmware name miss-match .. according to other
reports the firmware is not up to date or older/newer chip sets are not
supported this effects wifi and bluetooth (dual function chip)
did a
modprobe -r rtw88_8821ce
modprobe rtw88_8821ce
dmesg .. tail ..
[ 208.374092] rtw_8
note: same firmware appears to work for kernel 5.8 versions using
rtl8821ce-dkms .. no errors appear in dmesg ..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1911605
Title:
rebuild of rtl8821ce-dkm
It appears that firmware for rfc2 type antenna is not yet available as
per comment #2 at following link:
https://forum.siduction.org/index.php?topic=8134.0
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bug
other newer antenna styles also unsupported by rtw88_8821ce firmware..
it appears that rtl8821ce-dkms is antenna and firmware agnostic and work
for kernels 5.8 and lower .. at least one site has a module that fixes
the symbol issue and allows compilation of an rtl8821ce module ..
https://github.co
this did not get uploaded automatically: rtl8821ce-dkms.0.crash
** Attachment added: "rtl8821ce-dkms.0.crash"
https://bugs.launchpad.net/ubuntu/+source/rtl8821ce/+bug/1911605/+attachment/5454939/+files/rtl8821ce-dkms.0.crash
--
You received this bug notification because you are a member of U
yes that works I now have use of the rtl8821ce wireless connection
again..
thank you!
How soon will this be merged with hirsute?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1911605
Title:
rebuil
discovered during a manual partitioning install ..
found that fstab had an entry for /boot/efi mount vfat type pointed to
the /dev/sdb2 efi partition of the install media (USB)
deleted the fstab entry..
also deleted the mount point /boot/efi as no EFI partition existed on
an MBR based system (
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1890978
https://bugs.launchpad.net/ubuntu/+source/grub-installer/+bug/1891324
relevant info:https://bugs.launchpad.net/ubuntu/+source/grub-
installer/+bug/1890978/comments/4
--
You received this bug notification because you are a memb
Public bug reported:
Hirsute xubuntu daily march 31,2021 pre?beta
lenova sl500 intel graphics core2
already running hirsute on another partition
This is a test install
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: ubiquity 21.04.12
ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11
this bug is still not dead .. this is a duplicate of other reports
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922105
Title:
Installer crashed (grub not installed) on bios/mbr based system .. no
Artifacts left behind..
incomplete grub-install .. fixed with via a chroot -> grub-install
--target i386-pc /dev/sda
Reference to usbstick efi partition in fstab prevents boot .. fixed
commented out in /etc/fstab
then normal boot proceeds .. everything else appears normal
--
You received this
fix only present if auto resize is used .. will still fail with manual
resizing.
Auto resize adds a EFI fat32 partition during the resize. this prevents
the grub install failure.
if an EFI partition is not present the installer will fail ..
--
You received this bug notification because you are
this bug appears to be fixed in xubuntu apr 5, 2021 hirsute daily build
** Changed in: ubiquity (Ubuntu)
Status: New => Fix Released
** Changed in: ubiquity (Ubuntu)
Status: Fix Released => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, w
Public bug reported:
as per bug 1922105
ProblemType: Bug
DistroRelease: Ubuntu 21.04
Package: ubiquity 21.04.13
ProcVersionSignature: Ubuntu 5.11.0-13.14-generic 5.11.7
Uname: Linux 5.11.0-13-generic x86_64
NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair
ApportVersion: 2.20.11-0ubuntu
hirsute daily apr 5, 2021 xubuntu still has bug 1922105 for manual
partitioning grub fails to install if EFI partition is not present
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1922571
Title:
dup
confirmed that manual partition selection install without EFI fat32 partition
present will fail on grub install .. due to install media EFI fat32 partition
being substituted into new install fstab ..
autobug report generated .. with "duplicate of bug 1922105" title
** Changed in: ubiquity (Ub
So why does ubiquity not recognize that it is installing on an mbr
partitioned disk? and adjust accordingly.. seems rather wrong that the
install all fails at the install of grub .. especially as everything
else is ok..
also stealing 500 MB for an efi partition when it is not needed is
rather a w
after update .. not rebooted
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1860851
Title:
blueman-applet crashed with UnicodeDecodeError: 'utf-8' codec can't
decode byte 0x8e in position 4: invali
Public bug reported:
An upgrade to this version failed
Fails with the following ..
Setting up grub-efi-amd64-signed (1.140+2.04-1ubuntu24) ...
Unknown device "/dev/": Inappropriate ioctl for device
Unknown device "/dev/": Inappropriate ioctl for device
Unknown device "/dev/": Inappropriate ioctl
still running previous version
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872097
Title:
grub-efi-amd64-signed 1.140+2.04-1ubuntu24 throws an error during set-
up
To manage notifications about
*** This bug is a duplicate of bug 1872077 ***
https://bugs.launchpad.net/bugs/1872077
If I run dpkg-reconfigure it will install correctly .. but the
confirmation message is confusing
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu
>From bug#1872097
Ran sudo dpkg-reconfigure grub-efi-amd64-signed
response was confusing .. but I approved the install and everything appears to
boot normally.
after installing debconf-utils ran command from comment#2 above.
sudo debconf-get-selections | grep grub-efi
grub-pc grub-efi/install_
this crash happened to me on a fresh install of focal while doing the
first software update.
Blueman-applet was running in the panel and apparently is running again
after the crash ..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
ht
on a fresh install on a new partition of focal fossa (03/28) on
upgrading during the first boot into the install came across the same
error
did not "continue the install of grub-efi" so the disk was not altered
installed debconf-utils then ran debconf-get-selections | grep grub-efi
gave the foll
going back to the previous partition (trying to make it the default again)
I ran the following:
grub-install /dev/sda
Installing for x86_64-efi platform.
grub-install: warning: disk does not exist, so falling back to partition device
/dev/sda2.
grub-install: warning: disk does not exist, so fall
opps dropped a line at the end:
grub-install: error: disk `hostdisk//dev/sda2' not found.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872077
Title:
package grub-efi-amd64-signed 1.140+2.04-1ubun
ok: grub-install --target=x86_64-efi /dev/sda
works properly... sorry for the noise
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872077
Title:
package grub-efi-amd64-signed 1.140+2.04-1ubuntu24 f
When I pass the device it shuts up..
OKAY .. my initial report was bug 1872097 my original and still existing
install partition (sda5) for focal ( dec 2019) I used dpkg-reconfigure
there and of course then debconf-get-selections did not give the correct
info ..
So I created a new partition (sda6)
I was try to reproduce the bug on the same computer .. by adding another
install .. on another partition .. that worked .. bug was reproducible
..
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1872077
having multiple real installs on a computer of different versions of
linux (ubuntu spins, lts, development versions) allows testing in a real
environment .. as opposed to a vm .. was a standard practise prior to
vm's existing
--
You received this bug notification because you are a member of Ubunt
Public bug reported:
This happens under xubuntu and lubuntu (if using xfwm4 as window manager
instead of openbox)
with the latest update xfwm4-4.14.1-0ubuntu1 ..
previoius version had no issues..
first happened under xubuntu installed lubuntu to determine if graphic
driver was the issue but pro
** Attachment added: "a view of the screen with xfwm4 running"
https://bugs.launchpad.net/ubuntu/+source/xfwm4/+bug/1873318/+attachment/5355662/+files/Screenshot_2020-04-16_13-27-01.png
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubunt
note when booting through recovery mode and then starting xubuntu the
user screen is normal no staircasing.. (different graphic driver)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1873318
Title:
x
Processor : AMD Ryzen 3 3200U with Radeon Vega Mobile Gfx
Memory : 10112MB (985MB used)
-Display-
Resolution : 1600x900 pixels
OpenGL Renderer : AMD RAVEN2 (DRM 3.35.0, 5.4.0-24-generic, LLVM 9.0.1)
X11 Vendor : The X.Org Foundation
** Attachment added: "Xorg.0.log for information"
https://bugs.launchpad.net/ubuntu/+source/xfwm4/+bug/1873318/+attachment/5355667/+files/Xorg.0.log
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/18
Public bug reported:
install proceeded normally (manual partitioning) on reboot failed to
start X session .. rebooted to grub selection screen chose rescue mode
.. from the choices menu ran some checks then did updates install .. all
of the xorg-server files were installed automaticly .. then sele
yes the march 18, 2019 image boots correctly into lightdm(?) login
proceeds normally into xfce4/xubuntu
thank you for the quick fix.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1820430
Title:
fai
fresh disco install xubuntu-daily-03-22-2019 iso .. occurs shortly after first
login to xfce/xubuntu
while doing updates .. just before they completed ..
extra info:
apt show xfce4-panel
Package: xfce4-panel
Version: 4.13.4-1
Priority: optional
Section: universe/x11
Origin: Ubuntu
Maintainer: U
1 - 100 of 124 matches
Mail list logo
