Public bug reported:
Upgraded kernel available.
Restarted to 640x480 display.
No other resolutions apparently available.
Rebooted to previous kernel - display resolution now correct.
ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: xserver-xorg-video-nouveau 1:1.0.16-1
** Description changed:
Trying to connect to smartphone with a file manager and it hangs there.
+
+ Seems to work fine in 18.04.1, using a 18.10 live session it fails to
+ work.
journalctl -f output from when I try to connect to the phone gives this:
Nov 18 09:14:03 wolf-wolf
Public bug reported:
Trying to connect to smartphone with a file manager and it hangs there.
journalctl -f output from when I try to connect to the phone gives this:
Nov 18 09:14:03 wolf-wolf gvfsd[1615]: Device 0 (VID=04e8 and PID=6860) is a
Samsung Galaxy models (MTP).
Nov 18 09:14:10
@tjaalton - thanks - all done and tagged
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu.
Public bug reported:
removing the symlink is fine - but perhaps deal with it being called
when things go wrong for people ...
updated cosmic - which is now unbootable, whether that is due to this
breaking I'm not sure.
relevant section from /var/log/apt/term.log
Setting up console-setup
Changed bionic verification tag following comments #21, 22
** Tags removed: verification-needed-bionic
** Tags added: verification-done-bionic
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gvfs in Ubuntu.
On 13/04/18 08:05, Kai-Heng Feng wrote:
> How did you suspend the machine?
>
This prompted me to see if there was a difference using systemctl
suspend - there wasn't.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
>From the shutdown menu we use.
--
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/1760073
Title:
No network from suspend resume
Status in lightdm package in Ubuntu:
New
Status in
*** This bug is a duplicate of bug 1749546 ***
https://bugs.launchpad.net/bugs/1749546
On 09/04/18 19:09, Alistair Buxton wrote:
> *** This bug is a duplicate of bug 1749546 ***
> https://bugs.launchpad.net/bugs/1749546
>
> The Bluez timeout errors still show up in ~/.xsession-errors at
*** This bug is a duplicate of bug 1749546 ***
https://bugs.launchpad.net/bugs/1749546
Yep - checked with image I built for us Saturday morning. Was fixed
then.
** This bug has been marked a duplicate of bug 1749546
Booting a live session is slow - fontconfig regenerates its font cache
then it didn't
--
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/1760073
Title:
No network from suspend resume
Status in lightdm package in Ubuntu:
New
Status in linux package in
added a file to /lib/systemd/system-sleep with
#!/bin/sh
set -e
if [ "$2" = "suspend" ] || [ "$2" = "hybrid-sleep" ]; then
case "$1" in
pre) true ;;
post) sleep 1 && service network-manager restart ;;
esac
fi
and network coming out of suspend works ok.
--
You received
lspci -nnk
00:00.0 Host bridge [0600]: Intel Corporation 4th Gen Core Processor DRAM
Controller [8086:0c00] (rev 06)
Subsystem: Gigabyte Technology Co., Ltd 4th Gen Core Processor DRAM
Controller [1458:5000]
Kernel driver in use: hsw_uncore
00:01.0 PCI bridge [0604]: Intel
dmesg from suspend time:
[ 2652.902975] PM: suspend entry (deep)
[ 2652.902986] PM: Syncing filesystems ... done.
[ 2652.946758] Freezing user space processes ... (elapsed 0.001 seconds) done.
[ 2652.948257] OOM killer disabled.
[ 2652.948257] Freezing remaining freezable tasks ... (elapsed
lsusb:
Bus 002 Device 002: ID 8087:8000 Intel Corp.
Bus 002 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 001 Device 002: ID 8087:8008 Intel Corp.
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 004 Device 002: ID 2109:0812 VIA Labs, Inc. VL812 Hub
Bus 004 Device
Rechecked this (multiple times)
Using the GUI at Software & Updates>Additional Drivers appears to now
not remove conf files and hence user is left with 640x480px (assume
because of the blacklist file left in /etc/modprobe.d)
If one installs via apt and then purges - the nvidia conf file is
apport-collect failed to collect new information for this bug as nvidia
is no longer installed.
test@test-MBB-44608:~$ ls /etc/modprobe.d/
alsa-base.conf blacklist-framebuffer.conf dkms.conf
blacklist-ath_pci.conf blacklist-modem.conf iwlwifi.conf
blacklist.conf
someone turned up in #ubuntu+1 - they had nvidia-340.conf left after
uninstallation
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu.
https://bugs.launchpad.net/bugs/1761593
Title:
Uninstall left
Public bug reported:
Following a successful install and subsequent use of nvidia-340 -
uninstallation of nvidia via Additional Drivers led to a reboot to a
desktop at 640x480 px.
Investigation found an nvidia created file left on the system
blacklisting nouveau, deleted file and rebooted to
Daily 1st April:
ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez:
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to
activate service 'org.bluez': timed out (service_start_timeout=25000ms)
ERROR:dbus.proxies:Introspect error on org.bluez:/:
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1760073/+attachment/5097573/+files/ProcEnviron.txt
** Changed in: linux (Ubuntu)
Status: Incomplete => Confirmed
--
You received this bug notification because you are a member of Desktop
apport information
** Attachment added: "LightdmLog.txt"
https://bugs.launchpad.net/bugs/1760073/+attachment/5097570/+files/LightdmLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
apport information
** Attachment added: "LightdmGreeterLog.txt"
https://bugs.launchpad.net/bugs/1760073/+attachment/5097569/+files/LightdmGreeterLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1760073/+attachment/5097572/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
apport information
** Attachment added: "LightdmUsersConfig.txt"
https://bugs.launchpad.net/bugs/1760073/+attachment/5097571/+files/LightdmUsersConfig.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
apport information
** Attachment added: "LightdmDisplayLog.txt"
https://bugs.launchpad.net/bugs/1760073/+attachment/5097568/+files/LightdmDisplayLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
apport information
** Description changed:
Following a resume from suspend - no network available on machine.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: lightdm 1.25.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1760073/+attachment/5097542/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1760073/+attachment/5097541/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
apport information
** Attachment added: "LightdmUsersConfig.txt"
https://bugs.launchpad.net/bugs/1760073/+attachment/5097540/+files/LightdmUsersConfig.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1760073/+attachment/5097539/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
apport information
** Attachment added: "JournalErrors.txt"
https://bugs.launchpad.net/bugs/1760073/+attachment/5097531/+files/JournalErrors.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
apport information
** Attachment added: "Dependencies.txt"
https://bugs.launchpad.net/bugs/1760073/+attachment/5097538/+files/Dependencies.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
apport information
** Attachment added: "LightdmUsersConfig.txt"
https://bugs.launchpad.net/bugs/1760073/+attachment/5097535/+files/LightdmUsersConfig.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
apport information
** Attachment added: "ProcCpuinfoMinimal.txt"
https://bugs.launchpad.net/bugs/1760073/+attachment/5097536/+files/ProcCpuinfoMinimal.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
apport information
** Attachment added: "ProcEnviron.txt"
https://bugs.launchpad.net/bugs/1760073/+attachment/5097537/+files/ProcEnviron.txt
** Description changed:
Following a resume from suspend - no network available on machine.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
apport information
** Attachment added: "LightdmLog.txt"
https://bugs.launchpad.net/bugs/1760073/+attachment/5097534/+files/LightdmLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
apport information
** Tags added: apport-collected
** Description changed:
Following a resume from suspend - no network available on machine.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: lightdm 1.25.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
apport information
** Attachment added: "LightdmGreeterLog.txt"
https://bugs.launchpad.net/bugs/1760073/+attachment/5097533/+files/LightdmGreeterLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
apport information
** Attachment added: "LightdmDisplayLog.txt"
https://bugs.launchpad.net/bugs/1760073/+attachment/5097532/+files/LightdmDisplayLog.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
Public bug reported:
Following a suspend.
Get unlock screen - which then gets me a desktop.
Returned to unlock screen to enter password a second time.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: lightdm 1.25.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname:
Public bug reported:
Following a resume from suspend - no network available on machine.
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: lightdm 1.25.2-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-10.11-generic 4.15.3
Uname: Linux 4.15.0-10-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Ubuntu Mate - 75 second timeout noted in .xsession-errors
** Description changed:
Xubuntu seeing long first time boot to desktop from login.
- Possibly also causing the long time to desktop from try/install
- livesession dialogue.
+ Also causing the long time to desktop from try/install
Don't appear to be able to find the appropriate log in Ubuntu - however
grepping journalctl there for blue* gives me:
journalctl |grep blue*
Mar 14 17:51:27 ubuntu NetworkManager[985]: [1521049887.5999] Loaded
device plugin: NMBluezManager
Is this bug the result of trying to test suspend in a virtual machine?
** Changed in: xserver-xorg-video-nouveau (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xserver-xorg-video-nouveau in
** Bug watch added: GNOME Bug Tracker #790956
https://bugzilla.gnome.org/show_bug.cgi?id=790956
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1552792
Title:
gnome software
Public bug reported:
as in the title ...
was pointed at this for nautilus
https://gitlab.gnome.org/GNOME/nautilus/issues/154
see the same in thunar
ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gvfs 1.34.1-1ubuntu4
ProcVersionSignature: Ubuntu 4.14.0-13.15-generic 4.14.7
Uname: Linux
*** This bug is a duplicate of bug 1721189 ***
https://bugs.launchpad.net/bugs/1721189
** This bug has been marked a duplicate of bug 1721189
Thunderbird 1:52.4.0+build1-0ubuntu1 broken user interface
--
You received this bug notification because you are a member of Desktop
Packages,
probably a dupe of bug 1713344
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-software in Ubuntu.
https://bugs.launchpad.net/bugs/1713701
Title:
Gnome Software fails to run on 17.10 Beta 1 i386
Status in gnome-software package
needs gir1.2-secret-1
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to system-config-printer in Ubuntu.
https://bugs.launchpad.net/bugs/1709572
Title:
system-config-printer.py crashed with ValueError in require_version():
Namespace
downgrading to 1.5.9+20170619-0ubuntu1 and it works
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to system-config-printer in Ubuntu.
https://bugs.launchpad.net/bugs/1709572
Title:
system-config-printer.py crashed with ValueError in
*** This bug is a duplicate of bug 1704470 ***
https://bugs.launchpad.net/bugs/1704470
** This bug has been marked a duplicate of bug 1704470
playback fails using alsa in mpd
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
Public bug reported:
Using 4.11.0-10.15 kernel from -proposed playback fails using this
mpd.conf
##Pulseaudio
#audio_output {
# type"pulse"
# name"Local MPD"
# server "127.0.0.1"
#}
##Alsa
audio_output {
type "alsa"
53 matches
Mail list logo
