[Bug 1860268] Re: window titlebar is disturbed on all non-maximized windows
*** This bug is a duplicate of bug 1841718 *** https://bugs.launchpad.net/bugs/1841718 was fixed for me with common Ubuntu updates related to bug #1841718. ** This bug has been marked a duplicate of bug 1841718 [radeon] Rendering of combo boxes and tooltips is broken -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860268 Title: window titlebar is disturbed on all non-maximized windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1860268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860268] Re: window titlebar is disturbed on all non-maximized windows
** Also affects: mesa (Ubuntu) Importance: Undecided Status: New ** No longer affects: linux-signed-hwe (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860268 Title: window titlebar is disturbed on all non-maximized windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mesa/+bug/1860268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860268] Re: window titlebar is disturbed on all non-maximized windows
Also, some other desktop elements like tooltips, drop down lists or even the selection rubberband box of the screenshot feature are affected. It seems, that the the similarity of this is a comparable small *height*. The rubberband selection for instance is disturbed, if the enclosed height is about less than a few lines and this is totally independent from the width. For comparison, I create some squares with a bitmap editor: The quirks seems to have "shifted" band sections with a height of 8px. It disappear, if the height reaches about 8*8px. More exact, it aligned to height mod 8 and disappear, if (upper-lower) mod 8 >= 8. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860268 Title: window titlebar is disturbed on all non-maximized windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1860268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860268] Re: window titlebar is disturbed on all non-maximized windows
gjaekel@jelly:~$ lshw -C video WARNING: you should run this program as super-user. *-display description: VGA compatible controller product: Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM] vendor: Advanced Micro Devices, Inc. [AMD/ATI] physical id: 0 bus info: pci@:01:00.0 version: 00 width: 64 bits clock: 33MHz capabilities: vga_controller bus_master cap_list rom configuration: driver=radeon latency=0 resources: irq:31 memory:d000-dfff memory:fe9e-fe9f ioport:dc00(size=256) memory:c-d ** Description changed: * After todays package update, the window titlebar area of all windows is rendered in a disturbed way. * Package update include a kernel change to 5.3 from 5.0. The bug is not related to the kernel; it also happen with the last one. Therefore, it's related to the new graphic packages. * This don't happen if the window is maximized. - * This happen also on a second PC with idential hardware (Dell 755 & Radeon video card) + * This was also on a second PC with idential hardware (Dell 755 & Radeon HD 6450 video card) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-26-generic 5.3.0-26.28~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Jan 19 12:44:46 2020 SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860268 Title: window titlebar is disturbed on all non-maximized windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1860268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860268] Re: window titlebar is disturbed on all non-maximized windows
** Description changed: - * After todays package update, the window titlebar area of all windows is rendered in a disturbed way. + * After todays package update, the window titlebar area of all windows is rendered in a disturbed way. * Package update include a kernel change to 5.3 from 5.0. The bug is not related to the kernel; it also happen with the last one. Therefore, it's related to the new graphic packages. * This don't happen if the window is maximized. - * This was also on a second PC with idential hardware (Dell 755 & Radeon video card) + * This happen also on a second PC with idential hardware (Dell 755 & Radeon video card) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-26-generic 5.3.0-26.28~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Jan 19 12:44:46 2020 SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860268 Title: window titlebar is disturbed on all non-maximized windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1860268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860268] Re: window titlebar is disturbed on all non-maximized windows
** Attachment added: "Example of a disturbed titlebar area" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1860268/+attachment/5321529/+files/Titlebar_disturbed.Ubuntu18_04.20200119.png -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860268 Title: window titlebar is disturbed on all non-maximized windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1860268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860268] Re: window titlebar is disturbed on all non-maximized windows
** Attachment added: "dmesg from boot with kernel 5.3" https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1860268/+attachment/5321528/+files/dmesg.20200119 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860268 Title: window titlebar is disturbed on all non-maximized windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1860268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1860268] [NEW] window titlebar is disturbed on all non-maximized windows
Public bug reported: * After todays package update, the window titlebar area of all windows is rendered in a disturbed way. * Package update include a kernel change to 5.3 from 5.0. The bug is not related to the kernel; it also happen with the last one. Therefore, it's related to the new graphic packages. * This don't happen if the window is maximized. * This was also on a second PC with idential hardware (Dell 755 & Radeon video card) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: linux-image-5.3.0-26-generic 5.3.0-26.28~18.04.1 ProcVersionSignature: Ubuntu 5.3.0-26.28~18.04.1-generic 5.3.13 Uname: Linux 5.3.0-26-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.9 Architecture: amd64 CurrentDesktop: Unity:Unity7:ubuntu Date: Sun Jan 19 12:44:46 2020 SourcePackage: linux-signed-hwe UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: linux-signed-hwe (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug bionic ** Attachment added: "Today updated packages" https://bugs.launchpad.net/bugs/1860268/+attachment/5321524/+files/dpkg.log.20200119-114500 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1860268 Title: window titlebar is disturbed on all non-maximized windows To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-signed-hwe/+bug/1860268/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 763369] Re: Printer configuration was working, installed Samba4 for browsing samba shares, crashes now
Dear Scott, you're completely right: configuring a new computer I run into the same issue: * adding a remote printer (via ipp:), first tests works fine * after declaring it as the default, the Printer Administration Page on systemsettings fail. Running it from the console, it drops the same error messages as above. The solution was to copy the appropriate ppd file for the defined remote printer to /etc/cups/ppd/ . (I my case, i was able to copy it from the same directory on the remote server, because in my case the printer is attached there as a local one.) After restarting the cups service, the Administration Panel works, again. In addition, the print dialogs in other applications now choose the right default settings for the paper size. -- You received this bug notification because you are a member of Kubuntu Bugs, which is subscribed to kdeadmin in Ubuntu. https://bugs.launchpad.net/bugs/763369 Title: Printer configuration was working, installed Samba4 for browsing samba shares, crashes now To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/kdeadmin/+bug/763369/+subscriptions -- kubuntu-bugs mailing list kubuntu-b...@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/kubuntu-bugs
[Bug 305730] [NEW] on user change after resume, system hibernate again
Public bug reported: In general, hibernate (S3) and suspend action works fine. But there's a little ugly artefact: Probably different to others we're using this box at home as a "central workstation" for the members of our family. From that, there continously more than one user (X/gnome) session running. After resume, the screensaver prompts to unlock the last users session, what will work flawless. But as you derive from above, there's a big propability to use the "switch user" feature at this time. This will also work flawless in principle, will switch to the user selection screen. But after choosing a different user here and dismissing the password, the system will immediately hibernate again. After a wakeup, it continues "at this point" and will display the new users (unlocked) session. As said, this will not happen, if the "last" (i.e. current) user will unlock it's session. And it also will happen for some short time (maybe the current minute?), if we switch to another user after this first unlock. But if we wait a while before switching, the issue don't appear. This isn't a "fresh" bug: I'm currently using an up-to-date Ubuntu 8.04.1, but i watched this since more than one year, even on Ubuntu 7 and don't disappear until yet. From that, i decide to report it now. ** Affects: ubuntu Importance: Undecided Status: New -- on user change after resume, system hibernate again https://bugs.launchpad.net/bugs/305730 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 224802] Re: after sudo su (su -), gnome-terminal [or a virtual terminal "-bash"] "exit"s ("logout"s) with any single keypress
I'm also don't observe this currently on my Unbutu workstations, but
with "su -" on some of my Gentoo Server's, too. And this type of problem
is also reported by users of other distributions!
After switching to another user via "su - foo" i eithter get kicked out
immediately (the shell writes "exit" or "logout") or just after the
first keypress, if this isn't CR. Pressing CR will proceed to the next
prompt, any other will act like receiving a SIGHUP from somewhere. Note
that the pressed key is displayed before logout.
But sometime after leaving the system alone for a while or after
rebooting, all will work fine as expected for one try. With the next
try, the problem occurs again.
And more, sometime it will work with user account a, but not with b and
othertimes vice versa.
In addition, one of two nominal nearly-cloned boxes of one of my
clusters show the problem, the other one works flawless.
Some other guys wrote, that this only will happen with bash -- i don't
check it. But i don't think it's realy related to bash, su or sudo in
core.
I also try to get a hint from 'strace su - foo'. But using this type of
invocation, everythink works well, again! From this, i think it's some
very strange kind of a race condition. Maybe on slow hardware, maybe
just -- as another one reports -- on *single* (non-HT) CPU systems.
I observe it on my test boxes, which holds simple 1.6GHz P4 boards.
--
after sudo su (su -), gnome-terminal [or a virtual terminal "-bash"] "exit"s
("logout"s) with any single keypress
https://bugs.launchpad.net/bugs/224802
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 226279] Re: Kernel 2.6.24-17 - broken resume from suspend to RAM
As expected, 2.6.24-19 solves the issue and related artefacts for me, too. Thank you, John for discovering the core reason at #96. Two missing statements, and we are lost in space ;) Guido -- Kernel 2.6.24-17 - broken resume from suspend to RAM https://bugs.launchpad.net/bugs/226279 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 226279] Re: Kernel 2.6.24-17 - broken resume from suspend to RAM
Dear john and Tim john> Looking at the commit being reverted, its broken because the fix is not complete compared to mainline. john> [...] john> Noting especially the changes made upstream to kernel/time/timekeeping.c > @@ -178,6 +178,7 @@ static void change_clocksource(void) > + new->cycle_last = 0; > @@ -295,6 +296,7 @@ static int timekeeping_resume(struct sys_device *dev) > + clock->cycle_last = 0; Good or bad -- I didn't take a look on that clash before my guesses at #96. But it seems perfectly(?) match to my theory and -- if it holds -- to the proposed idea of a solution. It also matches some statements, that after waiting a longer time the system will continue to resume. This period might be the elapsed uptime until first suspend, because the TSC must at least re-incement to this uptime to "break" a delay loop somewhere. greetings Guido -- Kernel 2.6.24-17 - broken resume from suspend to RAM https://bugs.launchpad.net/bugs/226279 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 226279] Re: Kernel 2.6.24-17 - broken resume from suspend to RAM
Dear Tim, i wonder about this TSC issue the patch was designed for happens on my (and the other) machines, because it's have a single CPU without HT. The patch says "return some last value until the normal used one is higher than". From that: Will the TSC reset, if the CPU is suspended (powered down?). Then, after resume, the two calls will return the "last" values forever and *all* loops driven by that will hang. If this is the core reason, maybe the TSC value should be compared with some low value indicating that the CPU have a low uptime yet. And the "last" value should be lowered (or zeroed) in this case before the committed compare. Or -- even better, but may be more difficult -- the "last" value should be zeroed on some early initialisation stage of the CPU(s) greetings Guido -- Kernel 2.6.24-17 - broken resume from suspend to RAM https://bugs.launchpad.net/bugs/226279 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 226279] even on plain vanilla hardware
This is a "me too". But i want to note, that i'm running it on an comparatively "old" and plain vanilla surf/email station: P4/1.6Ghz (no HT), PATA-100, AGP- GraphicCard (Matrox MGA550), uhci (USB 1.1), no WLAN, ... may be this helps to exclude some things good luck Guido -- Kernel 2.6.24-17 - broken resume from suspend to RAM https://bugs.launchpad.net/bugs/226279 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 226566] MeTo: 2.6.24-17 breaks suspend/resume
*** This bug is a duplicate of bug 226279 *** https://bugs.launchpad.net/bugs/226279 ... unfortunately confirmed on my box, a Fujitsu/Siemens FSC Scenic S2. -- 2.6.24-17 breaks suspend/resume https://bugs.launchpad.net/bugs/226566 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
