*** This bug is a duplicate of bug 2038539 ***
https://bugs.launchpad.net/bugs/2038539
the duplicate bug appears as fixed
** Changed in: alsa-driver (Ubuntu)
Status: Confirmed => Fix Released
--
You received this bug notification because you are a member of Desktop
Packages, which
you can kill the process using killall, top, or other process control
tool without restarting your session
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-mahjongg in Ubuntu.
https://bugs.launchpad.net/bugs/2039369
Title:
similar bug #1991976 earlier version in a snap (jammy)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-mahjongg in Ubuntu.
https://bugs.launchpad.net/bugs/2039369
Title:
gnome-mahjongg locks up with high cpu usage on the second
Public bug reported:
I encountered this behaviour earlier during development of mantic and
opened a bug which I closed when the behaviour stopped .. later during
development .. unfortunately I have to file this bug again as the
problem has returned.. it has also been reported for an earlier
worse with snap based browser
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to alsa-driver in Ubuntu.
https://bugs.launchpad.net/bugs/2039358
Title:
Audio via bluetooth gets intermitent when a browser is started
Status in alsa-driver
Public bug reported:
listening to a fresh boot of mantic install .. sound works properly and
bluetooh headphones/speaker connection is flawless.. starting a browser
.. audio becomes choppy via bluetooth .. laptop speaker suffer no
degradation.. occurs with kernels above 6.5.0-5 see bug 2038539
This seems to have fixed itself.. I suspect other gnome/library/gtk
updates have fixed the issue.
I've declased this as invalid
** Changed in: gnome-mahjongg (Ubuntu)
Status: New => Incomplete
** Changed in: gnome-mahjongg (Ubuntu)
Status: Incomplete => Invalid
--
You received
can kill the game with top or kill command from terminal..
as it happens on either the first or second tile selection .. wondering
if a memory reset/free issue is involved
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-mahjongg
Public bug reported:
second game played always causes high cpu usage and mahjongg is
unresponsive .. can still exit desktop to reboot to stop high cpu
usage..
will investigate further as time permits
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: gnome-mahjongg 1:3.40.0-1
yes in a terminal app..
sudo dpkg -r kubuntu-desktop
sudo dpkg -r kubuntu-settings-desktop
sudo apt --fix-broken install
sudo apt reinstall kubuntu-desktop
will get around the blockage (as kubuntu-settings-desktop gets pulled
in by kubuntu-desktop both need to be temporarily removed)
--
You
had a quick look at the diff file between ubuntu thinderbird versions
78.2.1 and 78.2.2 .. there is a massive amount of deleted lines .. a lot
to do with twitter accounts .. is this on purpose or has something gone
amiss ..
--
You received this bug notification because you are a member of
Public bug reported:
Happened on upgrade from 78.2.1 to 78.2.2 lost all folder views ..
Groovy .. regular updates via proposed..etc. (xubuntu flavour)
Installed thunderbird 78.2.2 from thunderbird.net into personal home
directory works properly..
so it is an ubuntu regression issue ..
RE: Yoannjap
On my machine this is independent from the GSConnect extension. I did
not have it installed and installing/removing makes no difference. Bug
is there and is so consistently.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
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
I have mutter (3.35.91-1ubuntu1) installed and the bug is still there
(on 20.04 development branch) in both WPS and LibreOffice.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mutter in Ubuntu.
https://bugs.launchpad.net/bugs/1852183
Can also confirm being affected by this bug. Strangely it randomly
happens in LibreOffice for me, but constantly in WPS Office. When I copy
something it either pasts nothing (suggesting nothing was copied) or
pasts as a bitmap. Sometimes this bitmap shows all content that was
copied, sometimes a
Public bug reported:
system problem at login a few seconds after xfce desktop appears
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: cups-browsed 1.26.0-1
ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
Uname: Linux 5.4.0-9-generic x86_64
ApportVersion: 2.20.11-0ubuntu15
Happens to me too and only happens on the "Frequent" section (like Paul
above). The "All" section is fine.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-shell in Ubuntu.
https://bugs.launchpad.net/bugs/1842053
Title:
One or
seeing this on 18.04.3 xubuntu:
Aug 18 17:25:32 LAPTOP gpu-manager[806]: Error: can't open
/lib/modules/5.0.0-25-generic/updates/dkms
Any more info I can provide?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to ubuntu-drivers-common in
Two network printers on local LAN. Potentially more network printers
discoverable across VPN, but not configured in CUPS. Will report to
upstream.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
SAL_DISABLE_CUPS=true libreoffice
resolves the issue
None of the others do.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1838249
Title:
crash on startup
Status in
Same result.
I also tried adding
false
in case it was OpenCL instead of OpenGL.
Still crashes.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1838249
Title:
crash on startup
Here is what I did:
sudo apt autoremove --purge libreoffice*
sudo reboot
rm -Rf .config/libreoffice
sudo apt install libreoffice-writer
mkdir -p .config/libreoffice/4/user/
cp -a registrymodifications.xcu .config/libreoffice/4/user/
This is registrymodifications.xcu
Disabling OpenGL DOES NOT resolve the issue. I previously added
false
false
to the registrymodifications.xcu and it still crashes with the same traceback.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
Any hope of getting this looked at?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to libreoffice in Ubuntu.
https://bugs.launchpad.net/bugs/1838249
Title:
crash on startup
Status in libreoffice package in Ubuntu:
Confirmed
Bug
Same problem with or without --safe-mode:
localc --norestore --safe-mode
dbus[893]: arguments to dbus_message_iter_append_basic() were incorrect,
assertion "_dbus_check_is_valid_utf8 (*string_p)" failed in file
../../../dbus/dbus-message.c line 2754.
This is normally a bug in some application
Fine tuning: only one extra mount is necessary .. then plymouth
finishes very quickly .. and xorg/lightdm start normally!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1821609
** 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 (boot timing issues implicated)
--
You received this bug notification because you
okay I have another solution to the timing issue .. add two partition
mounts to fstab ..
my existing sda1 disco install has /home (sda2) and /home/store1 (sda5)
mounted via fstab .. this was the original install configuration .. thus
always a mount delay ..
to test .. added the same partions
of course the sda1 partition (on the SSD) has never failed to work properly no
matter which grub source (installs on sda1,sda6,sda7,sda8,sda9) is used
plymouth always appears when sda1 boots..
this disco version was installed jan 10 with a bootstrap log date of oct 13,
2018 .. it has been
okay turned back the clock .. to a spinning metal disk previously
installed in this hardware .. ran a number of test installs all work
fine .. cosmic/bionic/disco early version disco final all work boot
normally .. always ..
thus conclusion is a SSD is very fast and can respond to requests sooner
video of sda9 boot using sda9 install of grub (native grub) .. note absence of
plymouth .. flash at top edge of screen was missed .. note brief appearance of
lightdm .. short gap then lightdm reappears .. xorg.0.log.old records the
crash .. similar to others above
xorg.0.log records
video of sda8 non-native grub boot (a disco-xubuntu iso install) sda9
has installed grub (also a disco-xubuntu iso install ) will show in
next video uploaded
note the red flash .. plymouth attempt to start .. then cursor appears
and then lightdm briefly
** Attachment added: "video of failing
I will try to do videos for you tomorrow it is getting late in the day
here ..
a brief synopsis for now ..
history: this is standard grub arrangement as "installed by default"
used to work flawlessly with multiple partitions of various linux OS's
.. It is only since early march that I noticed an
bug is still present in disco xubuntu iso "final" 04-13.1-2019
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1821609
Title:
lightdm login screen briefly appears and then blanks out
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
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
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
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
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
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
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 ..
--
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
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"
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
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
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
** 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
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
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
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?
** 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
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 Desktop
Packages, which is subscribed to xorg-server in
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
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
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?)"
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
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
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
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
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
** 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 Desktop
Packages, which is subscribed to xorg in
*** 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)
*** 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
** 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
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
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
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
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
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
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 **:
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
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
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
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 Desktop
Packages, which is subscribed to cups-pk-helper
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
-0ubuntu9
Architecture: amd64
Date: Sun Sep 23 16:45:39 2018
ExecutablePath: /usr/bin/zenity
ProcCmdline: zenity --question --title=Install --text=Should\ a\ desktop\
file\ for\ /home/willem/Downloads/etcher-electron-1.4.4-x86_64.AppImage\ be\
installed?
Signal: 6
SourcePackage: zenity
Have tested the brltty package in bionic-proposed as instructed in
comment #12: v5.5-4ubuntu2.0.1
It works as expected.
After commenting out the "api-parameters Auth=keyfile" line in
brltty.conf and restarting the machine (just to be sure), my braille
display works completely in both text
With the latest updates, I can now see that the printer is low on ink
but the job continually restarts ..
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups-pk-helper in Ubuntu.
https://bugs.launchpad.net/bugs/1290533
Title:
I set the video to be public; you should be able to view it
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to network-manager-applet in Ubuntu.
https://bugs.launchpad.net/bugs/1767847
Title:
Xubuntu: clicking on network icon the network
Thanks to a member of the BrlTTY mailing list, my problem is solved. It
seems that the default authorization of BrltTTY under Ubuntu was no
longer working. Providing it with a dummy key-file was enough to get it
back to work - instantly.
The display came back to life immediately after these
Have just replayed the upgrade in a VirtualBox VM using a clean install
of Ubuntu 18.04.
Before the upgrade (of policy-kit), the braille display works (both
output and input).
After the upgrade and reboot, the same errors appear in /var/log/syslog:
Jul 18 11:49:43 test-VirtualBox brltty[409]:
Public bug reported:
$ lsb_release -rd
Description:Ubuntu 18.04 LTS
Release:18.04
$ apt-cache policy brltty
brltty:
Installed: 5.5-4ubuntu2
Candidate: 5.5-4ubuntu2
Version table:
*** 5.5-4ubuntu2 500
500 http://nl.archive.ubuntu.com/ubuntu bionic/main amd64 Packages
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
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 Desktop
Packages, which is subscribed to
Testing Xubuntu 18.10. Printer installation went fine. First print job
started fine as well. Then the crash occurred and the print job stopt
halfway through.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to cups-pk-helper in Ubuntu.
** Description changed:
Hi all,
My wifi connection disconnects constantly when I am connected to an
eduroam/govroam access point (protected EAP, MSCHAPv2).
The wifi driver is: rtl8812au-dkms.
Linux Xubuntu-18-04 4.15.0-22-generic #24-Ubuntu SMP Wed May 16 12:15:17
UTC 2018
** Description changed:
Hi all,
My wifi connection disconnects constantly when I am connected to an
eduroam/govroam access point (protected EAP, MSCHAPv2).
The wifi driver is: rtl8812au-dkms.
Linux Xubuntu-18-04 4.15.0-22-generic #24-Ubuntu SMP Wed May 16 12:15:17
UTC 2018
** Description changed:
Hi all,
My wifi connection disconnects constantly when I am connected to an
eduroam/govroam access point (protected EAP, MSCHAPv2).
The wifi driver is: rtl8812au-dkms.
Linux Xubuntu-18-04 4.15.0-22-generic #24-Ubuntu SMP Wed May 16 12:15:17
UTC 2018
Public bug reported:
Hi all,
My wifi connection disconnects constantly when I am connected to an
eduroam/govroam access point (protected EAP, MSCHAPv2).
The wifi driver is: rtl8812au-dkms.
Linux Xubuntu-18-04 4.15.0-22-generic #24-Ubuntu SMP Wed May 16 12:15:17
UTC 2018 x86_64 x86_64 x86_64
Same problem here with 4 1050TI cards. Installed 18.04, installed 390
driver, system doesn't boot anymore
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to mesa in Ubuntu.
https://bugs.launchpad.net/bugs/1752053
Title:
nvidia-390 fails
Public bug reported:
Using Xubuntu 18.04 daily on Notebook
product: 80UD (LENOVO_MT_80UD_BU_idea_FM_Lenovo ideapad 110-15ISK)
vendor: LENOVO
version: Lenovo ideapad 110-15ISK
serial: MP16LZHW
width: 64 bits
Linux Xubuntu-18-04 4.15.0-13-generic #14-Ubuntu SMP Sat Mar 17
Public bug reported:
Hello,
Ubuntu 17.10 64 bit
GNOME 3.26.2
nVIDIA GeForce GT620 driver 384.111
X-server 11.0, v1.19.5
Orca + braille enabled
$ lsb_release -rd
Description:Ubuntu 17.10
Release:17.10
$ apt-cache policy gdm3
gdm3:
Installed: 3.26.1-3ubuntu3
Candidate:
After fresh boot. Testing xubuntu 18.04.
Linux Xubuntu-18-04 4.15.0-12-generic #13-Ubuntu SMP Thu Mar 8 06:24:47 UTC
2018 x86_64 x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to udisks2 in Ubuntu.
Same problem here: Xubuntu 18.04, daily.
Mar 14 18:52:27 Xubuntu-18-04 gvfsd-metadata[1628]: g_udev_device_has_property:
assertion 'G_UDEV_IS_DEVICE (device)' failed
Mar 14 18:52:27 Xubuntu-18-04 gvfsd-metadata[1628]: message repeated 7 times: [
g_udev_device_has_property: assertion
Got the same problem on 17.04. I don't use Firefox. Using Thunderbird
and PHPStorm on daily basis. After some time (pretty random) unity-
panel-service takes all available RAM and I need to reboot to correct
the problem.
--
You received this bug notification because you are a member of Desktop
I am wondering whether I am seeing the same bug, or something else.
Please advice:
Running live session of Xubuntu Yakkety.
Linux xubuntu 4.8.0-11-generic #12-Ubuntu SMP Sat Sep 17 19:59:56 UTC 2016 i686
athlon i686 GNU/Linux
Starting gnome-software through the menu or through typing gnome-
I just tried another update && upgrade.
Many packages were updated.
But the problems with
libutempter0:i386
xterm
xubuntu-core
xubuntu-desktop
remain.
After a reboot, I tried another update && upgrade. Now I get messages
about hashes not being matched:
Failed to fetch
Public bug reported:
after upgrading to 16.04 (xubuntu) network drive not mounted
Asked by Willem Hobers on 2016-02-06
I upgraded from Xubuntu 14.04 to 16.04, because I would like to
attribute to the testing.
After the upgrade my network drive does not mount.
fstab
//192.168.178.73/Thuis
I came accross the same error during the upgrade from 14.04 to 16.04.
Halfway during the upgrade the screen went black and nothing seemed to happen.
After some time I rebooted (reset button). The boot process did not finish.
I got a terminal working and tried "sudo apt-get install -f".
That
1 - 100 of 118 matches
Mail list logo
