[Bug 1871503] [NEW] Samsung M2026 doesn't work (patch available)
Public bug reported: Splix is a free (libre) and open-source alternative to Samsung's closed- source ULD driver. Next to being free, Splix also offers better grayscale rendering than Samsung's ULD driver. Splix mainly provides a raster-to-QPDL filter (QPDL is Samsung's proprietary printer command language) and PPD files for respective printers. In the past, I successfully used Splix to print with a Samsung M2022. When I had to replace the printer with an almost identical M2026 (same features, same enclosure, just younger) I noticed that the M2026 does not work with Splix as supplied by Ubuntu. (Printer accepts print jobs but does only produce empty pages or does not emit a page at all.) I recently came across a patch (to Splix) from 2019 that makes the M2026 work by adjusting some details in the generated QPDL stream. The patch was committed here: https://gitlab.com/ScumCoder/splix (looks like a fork of the SourceForge repository where Splix was available in the past). Using the code from the Gitlab repo, I was able to successfully use the M2026 with Ubuntu 18.04. Is there any way to get this modification into the Ubuntu splix (printer-driver-splix) package? I'm willing to help by creating a patch that can be applied against the package's source if needed/desired. ** Affects: splix (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1871503 Title: Samsung M2026 doesn't work (patch available) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/splix/+bug/1871503/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1731786] [NEW] grafana reports problem in install script
Public bug reported: package grafana 2.6.0+dfsg-1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück (error message is in German due to user's locale. Translates to "sub- process installed post-installation-script returned error code 1". ProblemType: Package DistroRelease: Ubuntu 16.04 Package: grafana 2.6.0+dfsg-1 Uname: Linux 4.9.6-040906-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.10 Architecture: amd64 Date: Thu Nov 9 23:20:31 2017 ErrorMessage: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück InstallationDate: Installed on 2016-01-20 (662 days ago) InstallationMedia: Xubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) RelatedPackageVersions: dpkg 1.18.4ubuntu1.2 apt 1.2.24 SourcePackage: grafana Title: package grafana 2.6.0+dfsg-1 failed to install/upgrade: Unterprozess installiertes post-installation-Skript gab den Fehlerwert 1 zurück UpgradeStatus: Upgraded to xenial on 2016-04-24 (566 days ago) ** Affects: grafana (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package third-party-packages xenial ** Attachment removed: "Dmesg.txt" https://bugs.launchpad.net/ubuntu/+source/grafana/+bug/1731786/+attachment/5007916/+files/Dmesg.txt ** Attachment removed: "Df.txt" https://bugs.launchpad.net/ubuntu/+source/grafana/+bug/1731786/+attachment/5007915/+files/Df.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1731786 Title: grafana reports problem in install script To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/grafana/+bug/1731786/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1325675] Re: Indicator Plugin Area Refuses to Match Xfce Themes
I have the same problem when using the "Adwaita-X-dark" theme. When
using the "Bluebird" themes that ships with my Ubuntu 14.04, the
indicator plugin's background is dark blue (as it should be). When using
Adwaita, it is light grey as opposed to the rest of the panel which is
nearly black.
To me it looks like a definition in the theme is missing, too.
I solved it in my case by adding the following lines at the end of
~/.themes/Adwaita-X-dark/gtk-3.0/gtk.css
.xfce4-panel {
background-color: #22;
font: normal;
}
.xfce4-panel .button {
color: #ff;
}
(I took them from the Bluebird theme and changed the RGB color values to
match the Adwait-X-dark colors.)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1325675
Title:
Indicator Plugin Area Refuses to Match Xfce Themes
To manage notifications about this bug go to:
https://bugs.launchpad.net/xfce4-indicator-plugin/+bug/1325675/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1116999] Re: xfreerdp crashed with SIGSEGV in X509_get_issuer_name()
In case you need a server to reproduce the bug with, try connecting to uniapps.uni-rostock.de with arbitrary domain name, username and password. I am rather sure that this server uses a cert signed by an itermediate CA (because they do it for other services such as HTTP as well.) I tried to verify using openssl's s_client tool: # openssl s_client -connect uniapps.uni-rostock.de:3389 […] Certificate chain 0 s:/C=DE/ST=Mecklenburg-Vorpommern/L=Rostock/O=Universitaet Rostock/OU=ITMZ/CN=rds1.uni-rostock.de i:/C=DE/O=Universitaet Rostock/OU=Rechenzentrum/CN=Uni Rostock CA - G02/emailAddress=c...@uni-rostock.de 1 s:/C=DE/O=Universitaet Rostock/OU=Rechenzentrum/CN=Uni Rostock CA - G02/emailAddress=c...@uni-rostock.de i:/C=DE/O=DFN-Verein/OU=DFN-PKI/CN=DFN-Verein PCA Global - G01 2 s:/C=DE/O=DFN-Verein/OU=DFN-PKI/CN=DFN-Verein PCA Global - G01 i:/C=DE/O=Deutsche Telekom AG/OU=T-TeleSec Trust Center/CN=Deutsche Telekom Root CA 2 […] -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1116999 Title: xfreerdp crashed with SIGSEGV in X509_get_issuer_name() To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/freerdp/+bug/1116999/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1373005] Re: tulip 4.4 (Ubuntu 14.04) segfault on startup
Debian bug #723982 seems to be exactly the same issue: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723982 To me it looks like there are some serious bugs in tulip or one of the loaded libraries that lead to the crash on amd64 systems but work on i386. ** Bug watch added: Debian Bug tracker #723982 http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=723982 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1373005 Title: tulip 4.4 (Ubuntu 14.04) segfault on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tulip/+bug/1373005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1373005] [NEW] tulip 4.4 (Ubuntu 14.04) segfault on startup
Public bug reported: Crashed with segmentation fault unconditionally on each startup. Renders program unusuable. Output of GDB running tulip-dbg: Starting program: /usr/bin/tulip [Thread debugging using libthread_db enabled] Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". Gtk-Message: Failed to load module "overlay-scrollbar" [New Thread 0x7fffe1f64700 (LWP 13288)] [New Thread 0x7fffe1763700 (LWP 13289)] [New Thread 0x7fffe0f62700 (LWP 13290)] [New Thread 0x7fffdbfff700 (LWP 13291)] [New Thread 0x7fffdb7fe700 (LWP 13294)] [New Thread 0x7fffda796700 (LWP 13298)] [New Thread 0x7fffd9f95700 (LWP 13299)] [Thread 0x7fffdbfff700 (LWP 13291) exited] Program received signal SIGSEGV, Segmentation fault. 0x77dea138 in call_init (l=, argc=argc@entry=1, argv=argv@entry=0x7fffded8, env=env@entry=0x7fffdee8) at dl-init.c:78 78 dl-init.c: No such file or directory. (gdb) bt #0 0x77dea138 in call_init (l=, argc=argc@entry=1, argv=argv@entry=0x7fffded8, env=env@entry=0x7fffdee8) at dl-init.c:78 #1 0x77dea223 in call_init (env=, argv=, argc=, l=) at dl-init.c:36 #2 _dl_init (main_map=main_map@entry=0x99b380, argc=1, argv=0x7fffded8, env=0x7fffdee8) at dl-init.c:126 #3 0x77deec70 in dl_open_worker (a=a@entry=0x7fffd478) at dl-open.c:577 #4 0x77de9ff4 in _dl_catch_error (objname=objname@entry=0x7fffd468, errstring=errstring@entry=0x7fffd470, mallocedp=mallocedp@entry=0x7fffd460, operate=operate@entry=0x77dee9a0 , args=args@entry=0x7fffd478) at dl-error.c:187 #5 0x77dee3bb in _dl_open (file=0x977108 "/usr/lib/../lib/tulip//libogdfvisibility-4.4.0.so", mode=-2147483646, caller_dlopen=, nsid=-2, argc=1, argv=0x7fffded8, env=0x7fffdee8) at dl-open.c:661 #6 0x7592702b in dlopen_doit (a=a@entry=0x7fffd690) at dlopen.c:66 #7 0x77de9ff4 in _dl_catch_error (objname=0x6aa720, errstring=0x6aa728, mallocedp=0x6aa718, operate=0x75926fd0 , args=0x7fffd690) at dl-error.c:187 #8 0x7592762d in _dlerror_run (operate=operate@entry=0x75926fd0 , args=args@entry=0x7fffd690) at dlerror.c:163 #9 0x759270c1 in __dlopen (file=, mode=) at dlopen.c:87 #10 0x77acdb3d in tlp::PluginLibraryLoader::loadPluginLibrary (filename=..., loader=loader@entry=0x8c73d0) at /build/buildd/tulip-4.4.0dfsg2/library/tulip-core/src/PluginLibraryLoader.cpp:120 #11 0x77acdd6a in tlp::PluginLibraryLoader::initPluginDir (this=0x68beb0, loader=loader@entry=0x8c73d0) at /build/buildd/tulip-4.4.0dfsg2/library/tulip-core/src/PluginLibraryLoader.cpp:260 #12 0x77acec4e in tlp::PluginLibraryLoader::loadPlugins (loader=loader@entry=0x8c73d0, folder=...) at /build/buildd/tulip-4.4.0dfsg2/library/tulip-core/src/PluginLibraryLoader.cpp:67 #13 0x775f74c8 in tlp::initTulipSoftware (loader=loader@entry=0x8c73d0, removeDiscardedPlugins=removeDiscardedPlugins@entry=true) at /build/buildd/tulip-4.4.0dfsg2/library/tulip-gui/src/TlpQtTools.cpp:211 #14 0x0041c960 in main (argc=1, argv=) at /build/buildd/tulip-4.4.0dfsg2/software/tulip/src/main.cpp:169 Bug occurs with tulip 4.4.0dfsg2-2 on Ubuntu 14.04.1 LTS. ** Affects: tulip (Ubuntu) Importance: Undecided Status: New ** Tags: crash sigsegv tulip -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1373005 Title: tulip 4.4 (Ubuntu 14.04) segfault on startup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/tulip/+bug/1373005/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1311403] Re: Can't type password after resume.
I experienced the same behavior. After resuming from a suspend-to-RAM, I was not able to type a password in the lock-screen. After clicking into the password-entry field, no blinking cursor appeared and typing characters did not work. The buttons were clickable, though. I switched to a text TTY and killed gnome-screensaver to get back into my running GNOME session. I am using gnome-flashback session with lightdm. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1311403 Title: Can't type password after resume. To manage notifications about this bug go to: https://bugs.launchpad.net/unity/+bug/1311403/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 776779] Re: no way to require fprint OR password, which means no sudo over SSH/NX
Problem also occurs with 12.04. I agree that its quite annoying if you want to use sudo from within a (remote) SSH session. The only workaround I'm aware of is to wait for the fprint timeout and then enter your password. user@host:~$ sudo ls Scan ... finger on UPEK Eikon 2 Fingerprint verification error -22 [sudo] password for user: Unfortunately, the timeout is quite long (approx. 1 minute) and I couldn't find a way to configure it. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/776779 Title: no way to require fprint OR password, which means no sudo over SSH/NX To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libfprint/+bug/776779/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1066858] Re: seahorse-nautilus stores decrypted file without request
** Description changed: This is more a usability issue than a technical bug, despite very annoying. Situation: - I want to share sensible information with others and use a USB thumb drive for that. I plug-in the USB drive and double-click the file in nautilus to view its contents in gedit. I view the file and do not make any changes to it. I close gedit and remove the USB drive. + I want to share sensible information with others and use a USB thumb drive for that. + The files on the thumb drive are GPG-encrypted. I plug-in the USB drive and double-click an encrypted text file in nautilus to view its contents in gedit. I view the file and do not make any changes to it. I close gedit and unplug the USB drive. What I expected to happen: Since I did not make any changes to the text file, I expect the USB drive to be unchanged in any way. What happens: - Before launching gedit, seahorse-nautilius decrypts the file and deletes the original, encrypted file without further inquiry. After closing gedit the status is not repaired, i.e. the unencrypted file is left behind on the USB drive. + Before launching gedit, seahorse-nautilius decrypts the file, stores the plaintext file in the same directory as the encrypted, original file and deletes the original, encrypted file without further inquiry. After closing gedit the status is not repaired, i.e. the unencrypted file is left behind on the USB drive. I think that the default action in this case should not be a persistent change of the original file. Think of an archive file and file-roller. The default action there is to open the archive for reading, not decompressing it and deleting the archive file. - Some info about my setup: $ lsb_release -rd Description: Ubuntu 12.04.1 LTS Release: 12.04 gnupg 1.4.11-3ubuntu2.1 libnautilus-extension1a 1:3.4.2-0ubuntu4 nautilus 1:3.4.2-0ubuntu4 nautilus-actions 3.1.4-1build1 nautilus-data 1:3.4.2-0ubuntu4 seahorse 3.2.2-0ubuntu2 seahorse-daemon 3.2.2-1 seahorse-nautilus 3.3.1-0ubuntu1 GNOME -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1066858 Title: seahorse-nautilus stores decrypted file without request To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse-nautilus/+bug/1066858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 952084] Re: Cannot set solid color background when background fading is disabled
I can reproduce this bug with Ubuntu 12.04 and nautilus 1:3.4.2-0ubuntu8. Even worse, the desktop looks black when "solid" color is selected, but actually it is not drawn at all. If I move a window across the screen, it leaves a persistent "trail". The problem might be compiz-related. If I switch from compiz to metacity, the solid color background is draw correctly. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/952084 Title: Cannot set solid color background when background fading is disabled To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/952084/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1100320] Re: Annotation Font-Color is unreadable in Evince
Hi everyone! I am using the "Ambiance" GTK theme and was affected by this bug. I have Ubuntu 12.04.2 LTS installed on an AMD64 machine. I just downloaded and installed the following packages (with dpkg -i): evince_3.4.0-0ubuntu1.6_amd64.deb (md5sum: bb2e9efd4c8a20b29f2c054e43cda8d7) evince-common_3.4.0-0ubuntu1.6_all.deb (md5sum: 3cea48dba3415a523b06449daec9c1dd) libevince3-3_3.4.0-0ubuntu1.6_amd64.deb (md5sum: beed3be2fbebadb22e966a9a7e10fe04) The text in the annotation popup notes is now black on white background and is therefore perfectly readable. The issue is fixed for me. "Thank you" to everyone involved in fixing this! -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1100320 Title: Annotation Font-Color is unreadable in Evince To manage notifications about this bug go to: https://bugs.launchpad.net/evince/+bug/1100320/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1066858] [NEW] seahorse-nautilus stores decrypted file without request
Public bug reported: This is more a usability issue than a technical bug, despite very annoying. Situation: I want to share sensible information with others and use a USB thumb drive for that. I plug-in the USB drive and double-click the file in nautilus to view its contents in gedit. I view the file and do not make any changes to it. I close gedit and remove the USB drive. What I expected to happen: Since I did not make any changes to the text file, I expect the USB drive to be unchanged in any way. What happens: Before launching gedit, seahorse-nautilius decrypts the file and deletes the original, encrypted file without further inquiry. After closing gedit the status is not repaired, i.e. the unencrypted file is left behind on the USB drive. I think that the default action in this case should not be a persistent change of the original file. Think of an archive file and file-roller. The default action there is to open the archive for reading, not decompressing it and deleting the archive file. Some info about my setup: $ lsb_release -rd Description:Ubuntu 12.04.1 LTS Release:12.04 gnupg 1.4.11-3ubuntu2.1 libnautilus-extension1a 1:3.4.2-0ubuntu4 nautilus 1:3.4.2-0ubuntu4 nautilus-actions 3.1.4-1build1 nautilus-data 1:3.4.2-0ubuntu4 seahorse 3.2.2-0ubuntu2 seahorse-daemon 3.2.2-1 seahorse-nautilus 3.3.1-0ubuntu1 GNOME ** Affects: seahorse-nautilus (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1066858 Title: seahorse-nautilus stores decrypted file without request To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/seahorse-nautilus/+bug/1066858/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1000543] Re: Odd permissions on $HOME/.config/nautilus-actions make the directory unreadable by the owner
I'm also affected. I noticed the odd permissions today after a DejaDup error message. Interestingly, the permissions must have been right 11 days ago when I did the last backup on this machine, since I did not get an error message then. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1000543 Title: Odd permissions on $HOME/.config/nautilus-actions make the directory unreadable by the owner To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus-actions/+bug/1000543/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 861272] Re: No easy way to configure primary display
*** This bug is a duplicate of bug 800136 *** https://bugs.launchpad.net/bugs/800136 The solution described in https://bugzilla.gnome.org/show_bug.cgi?id=636216 -- dragging the small black top bar -- is absolutely not obvious to me. I just want to add that you can change the primary display programmatically (and driver-independent) using xrandr: $ xrandr --output VGA1 --primary -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/861272 Title: No easy way to configure primary display To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/861272/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 924082] Re: NM fails to connect to campus Wi-Fi network; wicd succeeds -- Centrino Ultimate-N 6300 iwlwifi
I am suffering from the same problem. My NIC is an Intel 6205: 03:00.0 Network controller: Intel Corporation Centrino Advanced-N 6205 (rev 34) Subsystem: Intel Corporation Centrino Advanced-N 6205 AGN Flags: bus master, fast devsel, latency 0, IRQ 49 Memory at f250 (64-bit, non-prefetchable) [size=8K] Capabilities: Kernel driver in use: iwlwifi Kernel modules: iwlwifi My observations are: Almost all WiFi networks work flawless using NetworkManager. However, with some networks I have persistent problems. I get a connection for a few minutes following boot-up, after that the NetworkManager icon goes to "scanning" and the syslog fllls up with "direct probe timed out messages. I experience this problem *only* in my university. They use exclusively Cisco equipment. I can look up the access point models if necessary. I am rather sure that NetworkManager is part of the problem. I experience the problem even when trying to connect to an unencrypted network at my university. However, when I stop NetworkManager and connect manually (iwconfig wlan0 essid FOO; ifconfig wlan0 up; dhclient wlan0) the bug does not occur even after hours. I also tried "iwconfig wlan0 power off" but this does not fix the "direct probe timeout" problem. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/924082 Title: NM fails to connect to campus Wi-Fi network; wicd succeeds -- Centrino Ultimate-N 6300 iwlwifi To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/924082/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 706259] Re: [915GM] DVI output not working after laptop wakeup
I noticed that the problem vanishes entirely if I disable KMS by adding "i915.modeset=0" to my kernel command line. Thus, disabling KMS and using UMS instead can be used as a workaround for Lucid. However, I recently dist-upgraded from Lucid to Maverick (10.10) and noticed that the bug is still present. To make things even worse, the xserver-xorg-video-intel version shipped with Maverick does no longer support UMS, so I am forced to use KMS and therefore can not use my workaround any longer. Symptoms with Maverick are the same as with Lucid: after a resume from suspend-to-RAM the DVI-output does not work anymore. My TFT just says "No signal". After a reboot the DVI is working again. This bug renders suspend-to-RAM almost useless to me. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/706259 Title: [915GM] DVI output not working after laptop wakeup -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 480220] Re: [i945] [i945][karmic] S-Video: PAL output is garbled
Absolutely the same here for me (i915GM in a Dell D410 used with D-Dock's TV output, Ubuntu 10.04, kernel 2.6.32-27-generic). After boot I have a stable NTSC output but can switch to PAL using "xrandr --output TV1 --set mode PAL". However, the picture gets unstable then: every time I move the mouse or have a lot of harddrive activity the TV picture jumps up and down, sometimes only some (rectangular) areas of the picture are affected. When there is no mouse movement the picture is stable. $ xrandr --verbose ... TV1 connected 1024x768+0+0 (0x4f) normal (normal left inverted right x axis y ... 1024x768 (0x4f) 26.9MHz *current +preferred h: width 1024 start 1025 end 1088 total 1120 skew0 clock 24.0KHz v: height 768 start 769 end 800 total 801 clock 30.0Hz When I create & use a new modeline with doubled dotclock like this: $ xrandr --newmode foo 54 1024 1025 1088 1120 768 769 800 801 ...I get a stable picture. BTW: If there is no connection to the TV set at boot time, xrandr will always show "TV1 disconnected" no matter if I plug in the TV out cable or not. Maybe both effects are caused by kernel mode settings. I have to try with disabled KMS. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/480220 Title: [i945] [i945][karmic] S-Video: PAL output is garbled -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 706259] Re: [915GM] DVI output not working after laptop wakeup
** Attachment added: "Xorg.0.log" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/706259/+attachment/1802998/+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/706259 Title: [915GM] DVI output not working after laptop wakeup -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 706259] Re: [915GM] DVI output not working after laptop wakeup
** Attachment added: "Output of dmesg" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/706259/+attachment/1802997/+files/dmesg.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/706259 Title: [915GM] DVI output not working after laptop wakeup -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 706259] Re: [915GM] DVI output not working after laptop wakeup
** Attachment added: "Output of lspci" https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/706259/+attachment/1802996/+files/lspci.txt -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/706259 Title: [915GM] DVI output not working after laptop wakeup -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 706259] [NEW] [915GM] DVI output not working after laptop wakeup
Public bug reported: Binary package hint: xserver-xorg-video-intel I use an external TFT display (Dell U2410) connected to a Dell docking station using the station's DVI output. My laptop is a Dell D410. I use Ubuntu 10.04.1 LTS. The DVI output works fine after a fresh boot but stops working when I put my laptop into sleep mode (suspend to RAM) and wake it up again. After the wakeup/resume the external TFT display reports "no signal". I am not able to turn the TFT on again after that. Neither "xrandr --output DVI1 --off" followed by a "xrandr --output DVI1 --mode 1920x1200" nor switching to another VT (Ctrl-Alt-F1 and -F7 again) will bring the DVI output back to life. However, the machine is up and running: I can use the laptop's internal display and reboot the machine to get my DVI back. I once tried a "vbetool post" on a textmode VT when the DVI output was gone: it turned on the DVI output and gave me a black screen with blinking cursor in the upper left corner but the X server was screwed and eventually I had to reboot. Please find attached the output of lspci, dmseg and the Xorg logfile *after* I resumed my laptop (e.g. the state were DVI is not working). At this very moment xrandr gives: $ xrandr --verbose Screen 0: minimum 320 x 200, current 1024 x 768, maximum 4096 x 4096 VGA1 unknown connection (normal left inverted right x axis y axis) Identifier: 0x41 Timestamp: 1814827 Subpixel: unknown Clones: CRTCs: 0 1 Transform: 1.00 0.00 0.00 0.00 1.00 0.00 0.00 0.00 1.00 filter: 1360x768 (0x45) 84.8MHz -HSync +VSync h: width 1360 start 1432 end 1568 total 1776 skew0 clock 47.7KHz v: height 768 start 771 end 781 total 798 clock 59.8Hz 1152x864@85.00 (0x46) 120.5MHz h: width 1152 start 1224 end 1352 total 1552 skew0 clock 77.6KHz v: height 864 start 865 end 868 total 902 clock 86.1Hz 1024x768@85.00 (0x47) 94.5MHz -HSync +VSync h: width 1024 start 1096 end 1200 total 1376 skew0 clock 68.7KHz v: height 768 start 771 end 775 total 809 clock 84.9Hz 1024x768 (0x48) 65.0MHz -HSync -VSync h: width 1024 start 1048 end 1184 total 1344 skew0 clock 48.4KHz v: height 768 start 771 end 777 total 806 clock 60.0Hz 800x600 (0x49) 40.0MHz +HSync +VSync h: width 800 start 840 end 968 total 1056 skew0 clock 37.9KHz v: height 600 start 601 end 605 total 628 clock 60.3Hz 800x600 (0x4a) 36.0MHz +HSync +VSync h: width 800 start 824 end 896 total 1024 skew0 clock 35.2KHz v: height 600 start 601 end 603 total 625 clock 56.2Hz 848x480 (0x4b) 33.8MHz +HSync +VSync h: width 848 start 864 end 976 total 1088 skew0 clock 31.0KHz v: height 480 start 486 end 494 total 517 clock 60.0Hz 640x480 (0x4c) 25.2MHz -HSync -VSync h: width 640 start 656 end 752 total 800 skew0 clock 31.5KHz v: height 480 start 489 end 492 total 525 clock 59.9Hz 640x480 (0x4d) 25.2MHz -HSync -VSync h: width 640 start 656 end 752 total 800 skew0 clock 31.5KHz v: height 480 start 490 end 492 total 525 clock 59.9Hz LVDS1 connected 1024x768+0+0 (0x48) normal (normal left inverted right x axis y axis) 246mm x 184mm Identifier: 0x42 Timestamp: 1814827 Subpixel: horizontal rgb Clones: CRTC: 1 CRTCs: 1 Transform: 1.00 0.00 0.00 0.00 1.00 0.00 0.00 0.00 1.00 filter: EDID: 00004ca3584a 000e0103801912780a87f594574f8c27 27505400080001010101010101010101 01010101010164190040410026301888 3600f6b80019000f 0018ee0274fe0054 3531333500313231584a0a2000fe 00ecd3c5b79168420001010a2020002e scaling mode: Full supported: None Full Center Full aspect 1024x768 (0x48) 65.0MHz -HSync -VSync *current +preferred h: width 1024 start 1048 end 1184 total 1344 skew0 clock 48.4KHz v: height 768 start 771 end 777 total 806 clock 60.0Hz 1024x768 (0x4e) 94.5MHz +HSync +VSync h: width 1024 start 1072 end 1168 total 1376 skew0 clock 68.7KHz v: height 768 start 769 end 772 total 808 clock 85.0Hz 1024x768 (0x4f) 78.8MHz +HSync +VSync h: width 1024 start 1040 end 1136 total 1312 skew0 clock 60.0KHz v: height 768 start 769 end 772 total
[Bug 689591] [NEW] Corrupted files with ecryptfs (filesize is multiple of 4k)
Public bug reported: Binary package hint: ecryptfs-utils I'm observing the following phenomenon on my system (Ubuntu 10.04, Dell laptop, encrypted home directory): I have a large amount of small files (approx. 4500 files, ascii text, around 3kb filesize) unpacked from an tar.gz archive into a subfolder within my encrypted home directory. I run a parser program on those files and the parser will stop if any file does not conform to an expected syntax. I now have the effect that the parser runs successfully through all my logfiles on one day, while it stops and complains about corrupt files on the next day. I investigated the reported files and noticed that these files are in fact corrupt: their filesize is always a multiple of 4k (usually 12288 bytes) and they contain a lot of binary garbage after their real contents. Sometimes contents from other logfiles show up within the "garbage area". The corrupt files are intact inside the tar.gz archive. So when I receive reports about corrupted logfiles I usually just delete all my logfiles, unpack the archive again, and then the parser runs without any errors. The logfiles are never written to on my system. The parser program just reads them. I'm a bit unsure if this effect is really caused by ecryptfs, so I checked the following: - According to S.M.A.R.T. diagnostics my hard-drive is in perfect condition (0 read errors, 0 remapped sectors, 0 pending sectors an so on). - A search for files which are multiple of 4k bytes in size *outside* of my home directory returned only files which are in fact that large. - A search for files which are multiple of 4k bytes in size *within* of my home directory returned some files which are obviously corrupted. - I ran fsck several times without getting any errors. - I looked into the logfiles of past boot-time fsck runs: no errors, too. I also watched out for ecryptfs-related error messages in my system logfiles, but all I found was the following error which occurred only once (whereas I have several file corruptions within the last two weeks): [10649.948257] ecryptfs_read_and_validate_header_region: Error reading header region; rc = [-4] Is it possible that this file corruption is indeed caused by ecrpytfs? What can I do to further narrow down the source of the problem? ProblemType: Bug DistroRelease: Ubuntu 10.04 Package: ecryptfs-utils 83-0ubuntu3 ProcVersionSignature: Ubuntu 2.6.32-26.48-generic 2.6.32.24+drm33.11 Uname: Linux 2.6.32-26-generic i686 Architecture: i386 Date: Mon Dec 13 11:08:08 2010 EcryptfsInUse: Yes InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release i386 (20091028.5) ProcEnviron: PATH=(custom, user) LANG=de_DE.utf8 SHELL=/bin/bash SourcePackage: ecryptfs-utils ** Affects: ecryptfs-utils (Ubuntu) Importance: Undecided Status: New ** Tags: apport-bug i386 lucid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/689591 Title: Corrupted files with ecryptfs (filesize is multiple of 4k) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 689591] Re: Corrupted files with ecryptfs (filesize is multiple of 4k)
-- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/689591 Title: Corrupted files with ecryptfs (filesize is multiple of 4k) -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 668029] Re: Icon too large + wrong icon displayed
** Attachment added: "Screenshot" https://bugs.launchpad.net/bugs/668029/+attachment/1714839/+files/nm-applet.png -- Icon too large + wrong icon displayed https://bugs.launchpad.net/bugs/668029 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 668029] [NEW] Icon too large + wrong icon displayed
Public bug reported: Every now and then the icon showing the current connection status in the panel is displayed far too large (see screenshot). In addition, the wrong icon is displayed. When taking the screenshot I had a wired connection (the tooltip in the screenshot is German and reads "Wired connection 'Auto eth0' is active"). I did not yet find a away to reliably reproduce the described behaviour. However, it seems that the wrong icon is only shown directly after I started a new session. When the network status changes (i.e. if I disconnect and reconnect manually) the correct icon in the correct size is shown. $ lsb_release -rd Description:Ubuntu 10.04.1 LTS Release:10.04 $ apt-cache policy network-manager-gnome network-manager-gnome: Installed: 0.8-0ubuntu3 Candidate: 0.8-0ubuntu3 Version table: *** 0.8-0ubuntu3 0 500 http://de.archive.ubuntu.com/ubuntu/ lucid/main Packages 100 /var/lib/dpkg/status (I filed this bug under the package "network-manager-applet" although /usr/bin/nm-applet belongs to "network-manager-gnome" on my system. However, in the bug tracker seems to be no package "network-manager- gnome".) ** Affects: network-manager-applet (Ubuntu) Importance: Undecided Status: New -- Icon too large + wrong icon displayed https://bugs.launchpad.net/bugs/668029 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
