Public bug reported:
I think this might be a duplicate of
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1870803 however,
I can't find out to add my machine information to it.
A little more information I can add - not sure if it's the same for
original reporter - when I first log into my
Looks like it's been fixed at some point
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/982742
Title:
Open file dialogue forgets sorting preferences
Status in
After going on the #radeon channel on Freenode, we narrowed the problem
down to the switcheroo-control package. We started by hand making an
xorg.conf file and disabling gpu-manager, but still had issues. Looking
at the dmesg log, we saw that the discrete gpu is enabled at first, then
disabled
** Also affects: switcheroo-control (Ubuntu)
Importance: Undecided
Status: New
** Changed in: lightdm (Ubuntu)
Status: New => Invalid
** Changed in: lightdm
Status: New => Invalid
--
You received this bug notification because you are a member of Desktop
Packages, which
** Attachment added: "xorg log"
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1692437/+attachment/5235697/+files/Xorg.0.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
Added gpu-manager log
It says "Unsupported discrete card vendor: 1002",
Does this mean my discrete card is no longer supported?
** Attachment added: "gpu-manager.log"
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1692437/+attachment/5235683/+files/gpu-manager.log
--
You received
I filmed my computer boot up to better show what happens. The right
monitor is on the integrated video card (the R7), and doesn't show
anything initially. The center and left monitor turn on and mirror each
other during boot, and show grub and most of the kernel and systemd
messages, then at some
** Attachment added: "dmesg log"
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1692437/+attachment/5235234/+files/dmesg.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
I've come across this again after upgrading to 18.10
$ xrandr --listproviders
Providers: number : 1
Provider 0: id: 0x56 cap: 0x9, Source Output, Sink Offload crtcs: 4 outputs: 3
associated providers: 0 name:KAVERI @ pci::00:01.0
$ sudo lspci -nn | grep
No worries. I can't reproduce it any more, I assume it was fixed at some
point.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/955546
Title:
gnome-terminal crashes with forked
Is there anything I can do to move this along?
I'm fairly certain it's a kernel or driver issue since zesty since I'm
currently running 16.04 on live USB and all three monitors work just
fine. I've tried using the 4.8 kernel from yakkety, but I couldn't get
it to boot, I'm assuming it was
I just saw this on 17.04
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screensaver in Ubuntu.
https://bugs.launchpad.net/bugs/1590661
Title:
Unable to unlock: "Time has expired"
Status in gnome-screensaver package in Ubuntu:
Some more information:
- If I switch my primary display adapter in BIOS to the onboard GPU, I can get
all three monitors and two cards working, but the framerate on the monitors
attached to the PEG GPU is so low that it's almost unusable.
- If I set the PEG GPU as primary display adapter, all
I'm beginning to think this is a driver issue. I have a builtin "Kaveri"
amd gpu, and pci Radeon HD 4850. I usually have the 4850 as my primary
card/monitor setup. However, since upgrading to Ubuntu 17.04, once
lightdm is started, only the monitor on the Kaveri works.
I dropped to VT1, and ran `X
lspci and lshw show 2 GPUs. The builtin one, and the actual card, but
xrandr only lists one provider.
$ xrandr --listproviders
Providers: number : 1
Provider 0: id: 0x56 cap: 0x9, Source Output, Sink Offload crtcs: 4 outputs: 3
associated providers: 0 name:KAVERI @ pci::00:01.0
Might be a
** Attachment added: "lshw output"
https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1692437/+attachment/4881175/+files/lshw.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to lightdm in Ubuntu.
Public bug reported:
I'm not 100% sure this is the right package to file the bug against, but
since upgrading to zesty the two monitors on my second GPU are no longer
detected once I reach the greeter screen at login time. However, both of
them display information during boot.
Let me know how I
@Chris: I'm not 100% sure, for my home machine it was either a Radeon HD
4850 or a Radeon R7 200 series.
I think this bug was "fixed" on both machines once I upgraded to Ubuntu
15.10. (Although on my work machine 15.10 caused a different system
freeze bug starting with that release that didn't
@Olivier: No, I haven't seen this bug in a while since I changed my
video cards. (I do still see the tooltip graphical artefacts when
hovering over the tabs, but it doesn't lock my browser.)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
I think this is/was either a bug in the radeon driver, or a faulty
graphics card. (however, it was only triggered when on the lightdm gtk
greeter screen). I've replaced my card with another one, and no longer
have this issue.
--
You received this bug notification because you are a member of
The only note-worthy log entries I see in that folder are in
x-0-greeter.log, and I'm not 100% sure they're related to this bug, I've
attached the log file.
I have just managed to reproduce this again:
1) I sshed into my machine from another machine to verify when my machine
crashes
2) On my
I have a new computer, and installed a new copy of Ubuntu 16.04 on it,
and I still get this issue. It's most likely related something new added
in 15.10 that is still causing issues in 16.04.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed
As an experiment, I tried logging out of my account and leaving it (over
the weekend). When I came back, the computer had frozen, and all the
login UI had disappeared. Perhaps a bug in X or lightdm?
** Also affects: lightdm
Importance: Undecided
Status: New
--
You received this bug
Another interesting data point: Last week I disabled the screensaver +
monitor turning off, and instead of locking the screen, I just turned my
monitors off, when I got to work this morning, my computer hadn't
frozen. So, this bug appears to be related to the lock screen. I'm not
sure what I'm
Probably not DPMS related, I tried disabling my monitor turning off, and
my computer still froze. Not sure what to do next.
** Summary changed:
- Complete system freeze some time after screensaver starts.
+ Complete system freeze some time after some inactivity
--
You received this bug
Not directly related to gnome-screensaver since I uninstalled it, and it
still crashed. Possibly related to the power management service, but not
sure.
** Also affects: ubuntu-gnome
Importance: Undecided
Status: New
** Changed in: gnome-screensaver (Ubuntu)
Status: New =>
** Attachment added: "output of journalctrl"
https://bugs.launchpad.net/ubuntu/+source/gnome-screensaver/+bug/1543782/+attachment/4568112/+files/journal.log
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-screensaver in Ubuntu.
Public bug reported:
The loading spinner in the tabs no longer matches the theme as of the
version 44 update. Attached is part of a screen shot that shows the
spinner with the default blue theme, whereas the rest of the application
uses my gtk theme. Before the last update, the spinner was a dark
Can the fix be back ported so I don't have to wait until October for it?
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/1453442
Title:
Destination folder (null) does not exist
Yay, looks like this got pushed through!
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1447701
Title:
Backport chromium-browser 43
Status in chromium-browser package in
Correction, Wily has version 42, but I see that debian jessie has
version 43. Can we get version 43 across the board?
** Summary changed:
- Upgrade chromium-browser to 42
+ Backport chromium-browser 43
** Description changed:
- Can we get an upgrade to version 42 now that it's the stable
*** This bug is a duplicate of bug 1447701 ***
https://bugs.launchpad.net/bugs/1447701
** This bug has been marked a duplicate of bug 1447701
Upgrade chromium-browser to 42
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
@victor, I can't replicate that with my tri-monitor setup, so it must
be a different bug (with same symptoms perhaps).
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to file-roller in Ubuntu.
https://bugs.launchpad.net/bugs/1453442
The apport window that pops up after crashes lists this bug as a
duplicate of https://bugs.launchpad.net/bugs/1402523 which does not
exist.
One thing I do notice that crashes it: if I hover over the tab name, the
tooltip will sometimes stay and become a white rectangle, if I then try
to show
Yes, that seems to be the case for the buttons; there was a process
running in the background. So the latter part of this report would be
that it's not finishing, not notifying of errors, and doesn't provide a
way to cancel/restart.
--
You received this bug notification because you are a member
Public bug reported:
Steps to reproduce:
- Open an archive with the file-roller gui
- Place the window over top of chromium
- Open a nautilus window
- Drag the contents of file-roller (to extract them) over to the nautilus
window making sure that the dragged content passes over the chromium
Public bug reported:
I have the duplicity backup scheduled to run every day, yet it has not
run in 6 days. What's more, the buttons to Restore.. and Back Up
Now... are disabled.
ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: duplicity 0.7.01-1ubuntu1
ProcVersionSignature: Ubuntu
Public bug reported:
Can we get an upgrade to version 42 now that it's the stable version?
** Affects: chromium-browser (Ubuntu)
Importance: Undecided
Status: New
** Tags: upgrade-software-version
--
You received this bug notification because you are a member of Desktop
Possible related bugs:
https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1377220
https://code.google.com/p/chromium/issues/detail?id=293008
https://code.google.com/p/chromium/issues/detail?id=418858
https://code.google.com/p/chromium/issues/detail?id=389816
This issue resolved for me with Ubuntu 14.10, but I seem to be the only
one for whom it did
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-settings-daemon in Ubuntu.
https://bugs.launchpad.net/bugs/1292398
Title:
Second screen
apport information
** Tags added: apport-collected
** Description changed:
Starting with a recent update to either my graphics card, or to
chromium, it (chromium) will seem to hang after resuming from a lock
screen. By hang, I mean it seems to refuse to redraw since it still
responds to
apport information
** Attachment added: HookError_chromium_browser.txt
https://bugs.launchpad.net/bugs/1400206/+attachment/4312307/+files/HookError_chromium_browser.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to
This is one of the most irritating bugs I've come across. At the moment it's
happening nearly every day on both my work and my home computers.
I just added additional information from my work computer in case it's useful.
--
You received this bug notification because you are a member of
apport information
** Attachment added: RelatedPackageVersions.txt
https://bugs.launchpad.net/bugs/1400206/+attachment/4312309/+files/RelatedPackageVersions.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in
apport information
** Attachment added: RelatedPackagesPolicy.txt
https://bugs.launchpad.net/bugs/1400206/+attachment/4312310/+files/RelatedPackagesPolicy.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in
apport information
** Attachment added: ProcEnviron.txt
https://bugs.launchpad.net/bugs/1400206/+attachment/4312308/+files/ProcEnviron.txt
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
Public bug reported:
Starting with a recent update to either my graphics card, or to
chromium, it (chromium) will seem to hang after resuming from a lock
screen. By hang, I mean it seems to refuse to redraw since it still
responds to mouse clicks on the close button. Here's the stderr output
on
Public bug reported:
I think this is probably a typo in the packaging; chromium created a
/use directory that I expect is supposed to be /usr
$ dpkg -S /use
chromium-browser: /use
$ ls /use
share
$ ls /use/share/
icons
$ ls /use/share/icons/
hicolor
$ ls /use/share/icons/hicolor/
scalable
$ ls
Workaround:
gconftool-2 --set /apps/metacity/general/button_layout --type string
close,minimize,maximize:
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1097125
Title:
The bug is still present with ubuntu 13.10:
amd-driver-installer-catalyst-13.1-legacy-linux-x86.x86_64
fglrx_8.970-0ubuntu1_amd64
Linux 3.11.0-13-generic #20-Ubuntu SMP Wed Oct 23 07:38:26 UTC 2013 x86_64
x86_64 x86_64 GNU/Linux
--
You received this bug notification because you are a member of
No, it's using chromium's title bar. See attached screenshot.
** Attachment added: chromium titlebar.png
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1097125/+attachment/3754594/+files/chromium%20titlebar.png
--
You received this bug notification because you are a member
@Chad, same thing, the buttons are in the top right corner.
$ apt-cache policy chromium-browser
chromium-browser:
Installed: 28.0.1500.71-0ubuntu1.13.04.1
Candidate: 28.0.1500.71-0ubuntu1.13.04.1
Version table:
*** 28.0.1500.71-0ubuntu1.13.04.1 0
500
Public bug reported:
I have deja-dup setup to backup to a password protected SMB share, when I set
it up I told it to remember the password. Now, when I start deja-dup and ask it
to do a back up, it opens the enter encrypted password dialogue, I click
next, it then skips a window, and lands
Public bug reported:
I switched around my monitor configuration so that I have 1 monitor on
my primary video card (1920x1080), and 2 monitors (1680x1024) on my
secondary video. The primary monitor's default resolution is higher than
the other two monitors so when it first started the other two
If I take one of the monitors from the second video card and plug it
into the primary, then everything works.
** Description changed:
I switched around my monitor configuration so that I have 1 monitor on
- my primary video card (1920x1080), and 2 monitors (1680x1024) on my
+ my primary video
Upstream bug report on xorg:
https://bugs.freedesktop.org/show_bug.cgi?id=65275
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/1186816
Title:
Gnome-shell and X die after changing
I'm not seeing this in my 12.10 install (with gnome-shell), but I am
seeing it in my 13.04. Would be nice for this to be fixed.
** Tags added: raring
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
Can we get the upstream fix backported? Pretty please.
--
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/974900
Title:
Menus split across multi monitors
Status in “libreoffice”
Unfortunately, the cables were not the issue. I tried with different
cables and different machines. I returned my drive and got a replacement
of a different brand, which has lasted longer than the other two
combined. I still think the issue may have been caused by issuing a
S.M.A.R.T, but I'm
Ok, I tried running a SMART test via gnome-disk-utility with the
mainline kernel, and still get these errors. It took about 4 hard resets
to get my SSD to show in BIOS this morning.
Excerpt:
Mar 27 21:15:36 jupiter kernel: [ 68.832057] ata4.00: exception Emask 0x0
SAct 0x0 SErr 0x0 action 0x6
Public bug reported:
I have an OCZ Petrol 128GB SSD, if I run S.M.A.R.T via gnome-disk-
utility my system freezes because it remounts the drive read only.
Checking my syslog I see a lot of unhandled error code messages. If I
then do a soft reboot, the SSD is not detected in POST; I have to hard
** Attachment added: Full syslog
https://bugs.launchpad.net/bugs/958188/+attachment/2888626/+files/syslog
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-disk-utility in Ubuntu.
https://bugs.launchpad.net/bugs/958188
Title:
Unfortunately, there isn't a crash report. I've tried to get a backtrace
in gdb, but gnome-terminal forks or something so I don't know how to
follow it.
I've also managed to reproduce this on precise.
--
You received this bug notification because you are a member of Desktop
Packages, which is
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to gnome-terminal in Ubuntu.
https://bugs.launchpad.net/bugs/955546
Title:
gnome-terminal crashes with forked command not found if path is too
long
Status in “gnome-terminal” package in
Public bug reported:
The affected package could also be the command-not-found package.
There seems to be a bug with the way either gnome-terminal or command-
not-found handles unknown commands that are forked. It also seems to be
dependent on the length of the full path.
My testcase (which may
I can't really reproduce it on Oneiric because you can't minimize
rhythmbox to tray. However, I can still reproduce it on Natty, I'm using
Metacity.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to rhythmbox in Ubuntu.
66 matches
Mail list logo
